On 06/08/2016 09:40, John Nelson wrote: > I saw the same crash error reported by George. (The only signal on 2m was a > JT65B signal - which QRA64 would have ignored.) > > This is a system error due to a segmentation fault. So jt9 would not have > reported any error - stopped dead in its tracks. This crash is not > reproducible. The Console error report is not much help either: > > Crashed Thread: 0 Dispatch queue: com.apple.main-thread > > Exception Type: EXC_CRASH (SIGSEGV) > Exception Codes: 0x0000000000000000, 0x0000000000000000 > Exception Note: EXC_CORPSE_NOTIFY > > Thread 0 Crashed:: Dispatch queue: com.apple.main-thread > 0 libsystem_kernel.dylib 0x00007fff8caf2db6 __psynch_cvwait + 10 > 1 libsystem_pthread.dylib 0x00007fff91db8728 _pthread_cond_wait + > 767 > 2 libgomp.1.dylib 0x0000000105e1752b gomp_sem_wait + 43 > 3 libgomp.1.dylib 0x0000000105e1780d > gomp_team_barrier_wait_end + 205 > 4 ??? 0x00007fc48a819400 0 + 140482114065408 > > Thread 0 crashed with X86 Thread State (64-bit): > > Logical CPU: 0 > Error Code: 0x02000131 > Trap Number: 133
Hi John & all, it is a little surprising that the error is reported in a thread that is probably blocked, do you have the rest of the crash dump report? With respect to sub-process error reporting, a while ago I enhanced the handling in WSJT-X such that the pop up error message box should capture all output from any failing sub-process. Advice to run from the command line is unlikely to glean any further information. As Joe invariably states, a recipe to reproduce an issue or a .WAV file that does the same is by far the best diagnostic aid. 73 Bill G4WJS. ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
