Message-ID:	<008701c2c1fa$ca2a9bd0$0100a8c0@acp42g>
From:	"Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
To:	<djgpp-workers AT delorie DOT com>
References:	<vt265sjj6vi DOT fsf AT zenia DOT red-bean DOT com> <7458-Tue21Jan2003210302+0200-eliz AT is DOT elta DOT co DOT il>
Subject:	Re: obsoleting the annotate level 2 interface
Date:	Wed, 22 Jan 2003 20:43:24 +1100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106
Reply-To:	djgpp-workers AT delorie DOT com

> > 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.

Andrew

- Raw text -