On 28/02/2021 13:12, David Schmocker wrote:

Process:               wsjtx [668]

Path: /Applications/wsjtx.app/Contents/MacOS/wsjtx

Identifier:            org.k1jt.wsjtx

Version:               v2.4.0 (2.4.0)

Code Type:             X86-64 (Native)

Parent Process:        bash [416]

Responsible:           wsjtx [668]

User ID:               501

Date/Time:             2021-02-28 07:12:00.072 -0600

OS Version:            Mac OS X 10.14.6 (18G8022)

Report Version:        12

Anonymous UUID: 1E2D07E1-9532-235B-3F34-D0F5B383F64D

Time Awake Since Boot: 1800 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)

Exception Codes:       KERN_INVALID_ADDRESS at 0x000000780000024e

Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11

Termination Reason:    Namespace SIGNAL, Code 0xb

Terminating Process:   exc handler [668]

VM Regions Near 0x780000024e:

    MALLOC_LARGE 0000000143335000-0000000143697000 [ 3464K] rw-/rwx SM=PRV

-->

    STACK GUARD 000070000f64e000-000070000f64f000 [    4K] ---/rwx SM=NUL  stack guard for thread 10

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0   org.k1jt.wsjtx              0x000000010a60f138 q65_encode + 40

1   org.k1jt.wsjtx              0x000000010a5cf0a1 genq65_ + 1157

2   org.k1jt.wsjtx              0x000000010a4b4d00 MainWindow::guiUpdate() + 9520

Hi David,

although we appreciate issue reports on WSJT-X, many of the crashes you are reporting are exactly the same. If you get a crash report that starts like this:

Process:               wsjtx [668]
Path:                  /Applications/wsjtx.app/Contents/MacOS/wsjtx
Identifier:            org.k1jt.wsjtx
Version:               v2.4.0 (2.4.0)
Code Type:             X86-64 (Native)
Parent Process:        bash [416]
Responsible:           wsjtx [668]
User ID:               501
Date/Time:             2021-02-28 07:12:00.072 -0600
OS Version:            Mac OS X 10.14.6 (18G8022)
Report Version:        12
Anonymous UUID:        1E2D07E1-9532-235B-3F34-D0F5B383F64D
Time Awake Since Boot: 1800 seconds System Integrity Protection: enabled
*Crashed Thread:        0*   Dispatch queue: com.apple.main-thread
Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x000000780000024e
Exception Note:        EXC_CORPSE_NOTIFY
*Termination Signal:    Segmentation fault: 11*
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [668]
VM Regions Near 0x780000024e:
    MALLOC_LARGE           0000000143335000-0000000143697000 [ 3464K] rw-/rwx 
SM=PRV
-->
    STACK GUARD            000070000f64e000-000070000f64f000 [    4K] ---/rwx 
SM=NUL  stack guard for thread 10
*Thread 0 Crashed:: Dispatch queue: com.apple.main-thread****0   org.k1jt.wsjtx                             0x000000010a60f138 q65_encode + 40*
1   org.k1jt.wsjtx                             0x000000010a5cf0a1 genq65_ + 1157
2   org.k1jt.wsjtx                             0x000000010a4b4d00 
MainWindow::guiUpdate() + 9520

The key similarities are that thread 0 terminated with a segmentation fault and the address being executed in thread 0 at the time was "q65_encode + 40".

There is no need to report this particular crash many times.

73
Bill
G4WJS.

_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to