This section provides instructions for using the debugger for the GAS.
To run the FGL debugger, you have to tell gasd not to run "fglrun" directly; instead, gasd must open a DOS command or a xterm window and run "fglrun -d".
<RESOURCE Id="res.dvm.wa" Source="INTERNAL">$(res.fgldir)\bin\fglrun.exe</RESOURCE>
<RESOURCE Id="res.dvm.wa" Source="INTERNAL">cmd /K start cmd</RESOURCE>
(Windows) <RESOURCE Id="res.dvm.wa" Source="INTERNAL">/home/test/xterm.sh</RESOURCE>
(Unix)
<DVM_AVAILABLE>10</DVM_AVAILABLE>
<DVM_AVAILABLE>60</DVM_AVAILABLE>
This change allows you 60 seconds in which to type your debug commands.fglrun -d test.42r
<<< Sets the debugger on program test.42r.b test:20
<<< Sets a break point.run
<<< Runs the application.Tip: You can also run gasd from the command line and override some the settings for res.dvm.wa:
gasd -E res.dvm.wa="cmd /K start cmd"
(Windows)
gasd -E res.dvm.wa="/home/test/xterm.sh"
(Unix)If you are using gasd as a service, you need to allow the service to interact with the desktop.
The following instructions assume that you are operating within a graphical
environment. If you are not operating within a graphical environment, simply enter the commands you want to process in the script.
To run the gasd, enter the following:
gasd -E res.dvm.wa="/home/test/xterm.sh"In the xterm.sh shell, you have:
/usr/X11R6/bin/xterm
(the complete path to xterm).
This removes all of the options given by gasd along with all error messages. A new xterm is opened. At this point, proceed as you would if you were running your applications from a Windows platform.