Thanks. This crash is occurring when J output is being written to the terminal in Qt.
Can you confirm that this is just the standard installation and not yet customized in any way, e.g. with changes to the profile script in ~bin, or a startup.ijs script in ~config? On Fri, May 23, 2014 at 10:14 PM, Murray Eisenberg <[email protected]>wrote: > I did try moving ~/install to /Applications on my boot drive. Still same > no go. > > Below is the complete Problem Report produced by OS X after I double-click > jqt.app and get the "jqt quit unexpectedly". Or if I double-click > jqt.command and see the error report in Terminal: > > [mine:~]$ /Applications/j64-802/bin/jqt.command ; exit; > /Applications/j64-802/bin/jqt.command: line 8: 4747 Segmentation fault: > 11 ./jqt > logout > > ========== > > Process: jqt [4645] > Path: /Applications/j64-802/*/jqt > Identifier: jqt > Version: 1.0 > Code Type: X86-64 (Native) > Parent Process: sh [4641] > Responsible: sh [4638] > User ID: 501 > > Date/Time: 2014-05-23 10:06:21.451 -0400 > OS Version: Mac OS X 10.9.3 (13D65) > Report Version: 11 > Anonymous UUID: 859389D0-8B1F-B2B8-DCF1-CCA6C9E663B6 > > Sleep/Wake UUID: E438AE7F-EA69-478B-A8C0-D854920AF4FB > > Crashed Thread: 0 Dispatch queue: com.apple.main-thread > > Exception Type: EXC_BAD_ACCESS (SIGSEGV) > Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008 > > VM Regions Near 0x8: > --> > __TEXT 0000000100000000-0000000100004000 [ 16K] > r-x/rwx SM=COW /Applications/j64-802/* > > Thread 0 Crashed:: Dispatch queue: com.apple.main-thread > 0 QtWidgets 0x00000001001f2344 > QPlainTextEdit::appendPlainText(QString const&) + 4 > 1 libjqt.dylib 0x000000010667a03b Joutput(void*, > int, char*) + 395 > 2 libj.dylib 0x000000010e761d23 jsto + 67 > 3 libj.dylib 0x000000010e75e4a8 jtjpr + 184 > 4 libj.dylib 0x000000010e8d073c jtjfwrite + 444 > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
