Mail Archives: djgpp-workers/1998/07/14/17:05:54
Eli Zaretskii wrote :
>
> If a program similar to symify is part of Binutils, as DJ suggested, it
> will solve both the problem of having to download BFD, and will make sure
> any format supported by DJGPP is automagically supported by symify.
Since addr2line is only similar (it needs the addresses on the
command-line) we will still need a new program to get at least
all the good features of our symify.
> > BTW: The sources for it are already part of the RHIDE source
> > distrib.
>
> Yes, I looked at it. The problem is (unless I miss something), you need
> the entire librhgdb.a to link gsymify.
Currently gsymify is only part of RHIDE so I took the shortest
way to implememnt it. librhgdb is needed only, since I did there
already all the work to initialize the gdb code (and with this
also the bfd code) to the needed file to examine. That means, gsymify
will need only a new function to initialize the libbfd and it will
work without librhgdb. (this code can be borrowed probably from
addr2line or so).
Analizing gsymify you will see, that there is only one function,
which does all the symbol examining stuff (the function symify()).
This function calls only code from libbfd. All the other stuff in
gsymify.c is there only to simulate the old symify program from
the core DJGPP.
> program like symify, it's probably next to impossible to add stabs
> support to DJGPP's src/debug functions. Too bad.
If you have ever seen the stabs handling source files in
gdb or libbfd, you will understand, that there is probably
nobody to implememnt this again for an other program when
it is easy to use libbfd.
Robert
itz.de/~sho/rho *
******************************************************
- Raw text -