Mail Archives: djgpp/2000/04/26/07:09:51
> From: Richard Dawe <richdawe AT bigfoot DOT com>
> Date: Tue, 25 Apr 2000 20:15:17 +0100
>
> Eli Zaretskii wrote:
> > The problem with using -gstabs+ by default is that SYMIFY doesn't
> > support stabs, so -gstabs+ renders stack tracebacks unusable, unless
> > you run the program inside GDB or RHIDE.
> >
> > If and when someone teaches SYMIFY about stabs, DJGPP will probably
> > switch to -gstabs+ as the default.
>
> Eli, ISTR that you had a BFD version of symify that did work with stabs+
> debugging. Maybe I am confused, but is this the case? I remember you sent
> me bfdsymify when I had some weird debugging problems, which we never got
> to the bottom of.
Yes, I do have a version of SYMIFY linked against the BFD library, and
that version should support stabs.
However, I use neither C++ nor stabs myself, so I don't have an easy
way of testing how well does it work, and debug whatever bugs might be
there.
At the time, I asked on djgpp-workers who would be interested to use
that version of SYMIFY and help me debug it, but never saw any
responses. Seems like no one is interested in getting this done.
(Testing and debugging a tool such as SYMIFY requires some knowledge
in how debug info is recorded in the executable, and it also requires
heavy use of Binutils programs such as objcopy and objdump. So this
is not a task for ``normal'' DJGPP users, which is why I didn't post
the request for help on this news group.)
For that matter, there's lots of things to be done in improving debug
support in general. For example, adding support for core files would
be nice. Adding code to SYMIFY to interpret additional parts of the
crash message, to make them tell their story in language understood by
humans, is another nice project.
It's too bad nobody is working in that area (AFAIK).
- Raw text -