Disabling startup has no effect. See my previous email. I'm convinced it's a code incompatibility caused by my needing to run a back-level of OS X.
On Tue, Mar 31, 2015 at 4:15 PM, chris burke <[email protected]> wrote: > Are you running anything when starting J, e.g. from a config/startup.ijs > script? If so, try without it. > > On 31 March 2015 at 07:06, Ian Clark <[email protected]> wrote: > >> Yes, it happens in a fresh session, in a freshly-restarted Mac. >> >> Here's what Mac Console tells me at the moment of a crash. >> The operative msg you'll see is: ...bin/jqt.command: line 14: 290 >> Segmentation fault ./jqt >> >> Tue 31/Mar/15 14:54:58 com.apple.launchd.peruser.501[121] >> (com.apple.ReportCrash.Self[321]) Job appears to have crashed: >> Trace/BPT trap >> Tue 31/Mar/15 14:54:58 com.apple.launchd.peruser.501[121] >> catch_mach_exception_raise_state_identity(): PID: 320 thread: 0xca03 >> type: 0xa code: 0x7fff5fbfdef4 codeCnt: 0x2 flavor: 0x7fff5fbfdf04 >> old_state: 0x7fff5fbfdf0c old_stateCnt: 0x2c new_state: 0x7fff5fbfe41c >> new_stateCnt: 0x7fff5fbfe418 >> Tue 31/Mar/15 14:54:58 com.apple.launchd.peruser.501[121] >> (com.apple.ReportCrash[320]) Job appears to have crashed: Trace/BPT >> trap >> Tue 31/Mar/15 14:54:58 com.apple.launchd.peruser.501[121] >> catch_mach_exception_raise_state_identity(): PID: 290 thread: 0xca07 >> type: 0xa code: 0x7fff5fbfdef4 codeCnt: 0x2 flavor: 0x7fff5fbfdf04 >> old_state: 0x7fff5fbfdf0c old_stateCnt: 0x2c new_state: 0x7fff5fbfe41c >> new_stateCnt: 0x7fff5fbfe418 >> Tue 31/Mar/15 14:54:58 [0x0-0x24024].jqt[279] >> /Applications/j64-803/jqt.app/Contents/MacOS/../../../bin/jqt.command: >> line 14: 290 Segmentation fault ./jqt >> Tue 31/Mar/15 14:54:58 com.apple.launchd.peruser.501[121] >> ([0x0-0x24024].jqt[279]) Exited with exit code: 139 >> >> Perhaps I ought to point out that I'm still running Snow Leopard. In >> the past I've noted an occasional code incompatibility with apps >> developed under a later OS X. So perhaps the only fix is to upgrade. >> (Which for operational reasons I don't choose to do just yet.) >> >> On Tue, Mar 31, 2015 at 2:50 PM, chris burke <[email protected]> wrote: >> > I also cannot reproduce this. >> > >> > Does it happen in a fresh session? Perhaps something happened earlier >> that >> > made JQt unstable. >> > >> > On 31 March 2015 at 05:41, Ian Clark <[email protected]> wrote: >> > >> >> In JQt, entering: >> >> >> >> 127 { a. >> >> >> >> or any expression outputting it to the session, such as >> >> >> >> a. >> >> 128 {. a. >> >> >> >> terminates JQt in a hard crash. >> >> >> >> A different value to 127 is ok: >> >> >> >> 126 { a. >> >> ~ >> >> 128 { a. >> >> � >> >> >> >> or any expression which doesn't actually output (127{a.) to the session, >> >> e.g. >> >> >> >> z=: 127 { a. >> >> >> >> >> >> JVERSION >> >> Engine: j803/2014-10-19-11:11:11 >> >> Library: 8.03.13 >> >> Qt IDE: 1.3.1/5.3.2 >> >> Platform: Darwin 64 >> >> Installer: J803 install >> >> InstallPath: /applications/j64-803 >> >> ---------------------------------------------------------------------- >> >> For information about J forums see http://www.jsoftware.com/forums.htm >> > ---------------------------------------------------------------------- >> > For information about J forums see http://www.jsoftware.com/forums.htm >> ---------------------------------------------------------------------- >> For information about J forums see http://www.jsoftware.com/forums.htm >> > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
