To run the FGL debugger, the dispatcher must open a DOS command or a xterm window and
then run fglrun -d.
-
In the GAS configuration file (default
%FGLASDIR%/etc/as.xcf), change:
<RESOURCE Id="res.dvm.wa" Source="INTERNAL">
$(res.fgldir)\bin\fglrun.exe</RESOURCE>
to:
<RESOURCE Id="res.dvm.wa" Source="INTERNAL">
c:\fjs\gas\debug.bat</RESOURCE>
(Windows®) for example, where debug.bat contains
cmd /K start cmd
-
In the application configuration file, change the DVM availability timeout value to allow
you time to type your debug commands.
For example, change:
<DVM_AVAILABLE>10</DVM_AVAILABLE>
to:
<DVM_AVAILABLE>60</DVM_AVAILABLE>
This change allows you 60 seconds
in which to type your debug commands.
-
Restart the dispatcher.
(The dispatcher must be restarted whenever you modify the application server configuration
file in order for the changes to take effect.)
-
Enter the application URL in your browser.
This opens a shell window.
-
Type the commands to run the application:
fglrun -d test.42r <<< Opens the debugger tool and sets it
on program test.42r.
(fgldb)b test:20 <<< Sets a break point
at line 20.
(fgldb)run <<< Runs the application.
This refreshes the browser, like the FGL debugger does with the GDC.
Tip:
You can also run the dispatcher from the command line and override some of the settings for
res.dvm.wa:
httpdispatch -E res.dvm.wa="cmd /K start cmd" (Windows)