Mail Archives: djgpp/1998/09/13/17:49:12
I found myself rather unsatisfied with the other replys to your problem I
saw in this group ( they confused me, and I know what it meens! ).
You do have to run SYMIFY if you are using MS-DOS ( I do not suggest rhIDE,
there are tools far more advanced and much simpler to use ).
When compiling, make sure you use the -g command line option. Also, do NOT
use the -s command line option, since that will remove the information
generated by the -g switch.
The -g switch stores variable, function names, and line numbers in the
executable ( making it rather large, but easily debuggable ).
When your program crashes, run SYMIFY using the name of your executable as a
command line parameter:
symify myprog.exe
This must be done while the error message is still on the screen.
Symify will write to the screen the source file names and line numbers of
the traceback
( That would be this bit below here )
>Call frame traceback EIPs:
> 0x0000193c
> 0x00001cb6
> 0x000016d7
> 0x00002e62
Onto the screen, so you can see where the error that caused the crash
occured.
Also, if you have compiled with the -g switch, you can use GDB, the command
line debugger. For its simplest use, type GDB followed by the executable
name:
gdb myprog.exe
WHen the command line shows again, type "r" ( without quotes ) and hit
enter. This will run the program. When the program crashes, GDB will give
you the same infomration as SYMIFY and more. The command "help" will tell
you more GDB options, and the command "q" will exit GDB.
Do note, sometimes certain errors ( those dealing with illegally writing to
memory ) may sometimes not occur while using GDB, because of the way in
which it slighty changes execution of the running program.
Sean Middleditch
of
AwesomePlay Productions
http://www.angelfire.com/biz/aweplay
aweplay AT hotmail DOT com
- Raw text -