Mail Archives: djgpp/2002/04/07/11:25:12
> From: CBFalconer <cbfalconer AT yahoo DOT com>
> Newsgroups: comp.os.msdos.djgpp
> Date: Sun, 07 Apr 2002 13:57:44 GMT
> Is there any special reason that addr2line is not incorporated in
> symify? Why have the user need to transcribe hex addresses from
> the screen?
I don't understand: SYMIFY does translate hex addresses into human
readable file name and line number information. addr2line does the
same, except that its UI is different.
Perhaps you meant why isn't the equivalent of SYMIFY part of the
standard library exit code?
If you want a version of SYMIFY that knows about debug formats other
than COFF (like stabs or DWARF2), like addr2line does, you can use
bfdsymify.exe from the GDB 5.1.1 distribution. bfdsymify has the same
UI as SYMIFY.
> Another convenience: At least with 4dos an environment variable
> CMDLINE is left, so symify without parameters could use that by
If you want to use CMDLINE to get the name of the program, there's no
need for that: the crash message includes the full path to the
program's executable. This is better than CMDLINE, since the latter
doesn't tell where to look for the .exe file.
- Raw text -