On 29/04/2019 19:18, Michael Johnston wrote:
I’m new to this list, so I’m not sure what the protocol is for reporting bugs.
Please redirect me as appropriate.
I’ve just downloaded and installed RC5 on a Mac running OSX Mojave (10.14.3).
(I previously had WSJT-X 2.0.1 installed). The app crashes at startup, with a
popup dialog box saying ‘WSJT-X quit unexpectedly.” The stack trace is below.
Process: wsjtx [34825]
Path: /Applications/wsjtx.app/Contents/MacOS/wsjtx
Identifier: org.k1jt.wsjtx
Version: v2.1.0-rc5 (2.1.0-rc5)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: wsjtx [34825]
User ID: 501
Date/Time: 2019-04-29 14:17:12.131 -0400
OS Version: Mac OS X 10.14.3 (18D109)
Report Version: 12
Anonymous UUID: B1ED34EC-8FF8-B795-1683-7639C5437ADC
Sleep/Wake UUID: 3E5BFD17-9D21-4A10-A0DC-21720D0ED10C
Time Awake Since Boot: 3400000 seconds
Time Since Wake: 940000 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 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [34825]
VM Regions Near 0:
-->
__TEXT 000000010e59e000-000000010ea66000 [ 4896K] r-x/rwx
SM=COW /Applications/wsjtx.app/Contents/MacOS/wsjtx
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libgfortran.5.dylib 0x0000000113d622da
_gfortran_concat_string + 23
1 org.k1jt.wsjtx 0x000000010e6e0c3d azdist_ + 93
2 org.k1jt.wsjtx 0x000000010e605cd5
MainWindow::on_dxGridEntry_textChanged(QString const&) + 389
3 org.k1jt.wsjtx 0x000000010e615a72
Hi Michael,
this is exactly the right place to report issues, and thanks for the
issue report. I have managed to reproduce it and am looking into it
right now.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel