Mail Archives: djgpp-workers/2003/01/22/12:14:05
On Wednesday 22 January 2003 11:43, Andrew Cottrell wrote:
> > > GDB seems to support two different ways of doing detailed annotations
> > > of its output for consumption by other programs: MI and 'set annotate
> > > 2'. I don't think annotation level 2 has many active users, if any at
> > > all. It pervades GDB's code. Would it make sense to put 'set
> > > annotate 2' on the path to obsolescence?
> >
> > It's possible that RHIDE, the Turbo-C compatible IDE developed for
> > DJGPP, uses "annotate 2" (RHIDE has the GDB core built into it). I CC
> > the DJGPP developers' mailing list, in the hope that someone who knows
> > more than myself about the debugging engine of RHIDE will tell whether
> > I'm wrong.
>
> I have the source for Rhide 1.5.0 snapshot and I had a look and there are a
> few references to annotate with regards to libgdb.a, but I do not know what
> I am looking for. If Andris doesn't respond could you point my in the
> appropriate direction.
Debugger support has been changed rather little changed gdb-4.1[78] times.
There are practically only maintainance related changes due to
incompatibilities with new GDB versions. It really uses annotate_*()
procedures (There are overriden them to get RHIDE internal source called from
GDB).
Changing to something newer would perhaps be nice, but I don't even know when
I'll touch DJGPP build of RHIDE at all, as I'm using DJGPP now rather little
mostly for maintaining existing programs, that generally work without much
problems. My current development projects are mostly for Linux.
Also Robert wrote in private message, that he hopes to get 1.5 out at the end
of previous year, but this didn't happen: I also haven't asked him once more.
Andris
- Raw text -