>>  <<  Ndx  Usr  Pri  Phr  Dic  Rel  Voc  !:  wd  Help  User

Starting J - Profile Errors

The profile script is loaded (which in turn loads several other scripts) after the J front and J engine start. A profile error can be difficult to debug.

In jconsole you see the error but have no information on which script has the error.

In jwd there probably isn't even an ijx window to show the error so all you see is a message box:

   Error and no IDE window for debugging.
Debugging profile bugs can be difficult, but the following steps may help.

1. Start jwd or jconsole without the profile.

   windows> \j504\j.exe -jprofile
   windows> javaw -jar \j504\j.jar -jprofile
   unix>    ~/jw -jprofile
   windows> \j504\jconsole -jprofile
   unix>    ~/j505/jconsole -jprofile
The jwd with -jprofile gives a bare bones ijx window.

2. 1!:45'' is the profile that is normally loaded. First make sure that it exists.

   1!:45''
c:\j504\profile.ijs
   #1!:1<1!:45'' NB. size of profile
2805
3. Define DISPLAYLOAD_j_ as 1 before loading profile so that scripts are reported as as they are loaded.
   DISPLAYLOAD_j_=: 1
   0!:0<1!:45''
c:\j504\system\main\sysenv.ijs
c:\j504\system\main\stdlib.ijs
...
4. Use a texteditor to examine the script with the error and fix it.

5. DISPLAYLOAD_j_ as 1 will report scripts as they are loaded by require and load. Setting it to 0 stops the reporting.


>>  <<  Ndx  Usr  Pri  Phr  Dic  Rel  Voc  !:  wd  Help  User