As regards jconsole.sh not running from your file manager, that sounds
like the way your file manager handles executable scripts. The script is
executable, and on my Linux Mint, clicking an executable script in the
Nemofile manager displays a prompt "do you want to run jconsole.sh or
display its contents?".
Here is the listing of jconsole.sh and jqt.sh:
-rwxr-xr-x 1 brian brian 107 Nov 6 15:20 jconsole.sh
-rwxr-xr-x 1 brian brian 126 Nov 6 15:20 jqt.sh
As you can see, they are both executable. When I click on jconsole.sh
in the file manager nothing happens. When I click on jqt.sh it invokes
J. This suggests that it is not a problem with the file manager.
I can reliably generate a segmentation fault. The method is:
Open a terminal
Navigate to J64-806
./jqt.sh
This opens Term. When I close it there is a segmentation fault.
As an experiment, I opened three terminals and invoked J in each of them.
When I closed the first Term I got:
./jqt.sh: line 8: 8166 Segmentation fault bin/jqt
When I closed the second Term I got:
./jqt.sh: line 8: 8175 Segmentation fault bin/jqt
When I closed the third Term there was no segmentation fault. Other
times there was a segmentation fault.
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
