You did not say anything about the machine with the problem. It looks like it's an OSX machine, but what version of OSX? And, what kind of hardware are you running on?
(By the way, another possibility, besides a damaged installation, is that there's something else running on that machine which is interfering with J.) When J crashes, the machine is probably offering you the possibility of reporting the error. If you allow that, the first thing it will do is pop up a bunch of information about what went wrong (including a window which, if you scroll down, will show you a stack backtrace). Some of the information there might be useful (and the stack backtrace might be informative). -- Raul On Wed, Feb 2, 2022 at 9:54 AM Arthur Anger <[email protected]> wrote: > > All-- > My current Mac session shows a different initiation, with no segment fault: > Last login: Tue Feb 1 18:12:50 on ttys000 > Arthurs-MacBook:~ ala$ /Applications/j902/bin/jhs.command ; exit; > > J HTTP Server - init OK > > What might trigger the difference? Thanks. > --Art > > > On 1Feb 2022, at 10:08 PM, Arthur Anger <[email protected]> wrote: > > > > Staff-- > > At intiation, the Terminal log shows: > > /Applications/j902/bin/jhs.command: line 2: 53470 Segmentation fault: 11 > > "`dirname "$0"`/jconsole" ~addons/ide/jhs/core.ijs -js " init_jhs_'' " > > > > Even so, the session opens, and I may compute for even a hundred commands, > > and then the server will quit. Two or three of the occasions were after > > entering debugging commands. > > > > Where can I find information helpful to you in tracking down this/these > > bugs? Thanks. > > --Art > > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
