Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Bob Rossi <bob_rossi@cox.net>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: "Jain, Rohit" <Rohit_Jain@mentor.com>, gdb@sources.redhat.com
Subject: Re: GDB Annotations : support plan
Date: Wed, 30 Jan 2008 00:21:00 -0000	[thread overview]
Message-ID: <20080130002103.GC28482@brasko.net> (raw)
In-Reply-To: <18335.47450.501387.805867@kahikatea.snap.net.nz>

On Wed, Jan 30, 2008 at 12:40:10PM +1300, Nick Roberts wrote:
> Jain, Rohit writes:
>  > Hi,
>  > 
>  > GDB is now supporting GDB/MI interface, and the annotation mechanism has
>  > now become obsolete.
>  > 
>  > Is there any plan to completely discontinue the support for annotations
>  > in future?
> 
> Yes.

Agreed.

>  > If yes, and if you know approximate release period that annotations are
>  > going to exist, please let me know.
> 
> AFAIK here is no timescale.

Hopefully not to soon. I still use them in my front end, but will
hopefully in 2008 switch to MI.

>  > If no, then is it safe to assume that GDB/MI interface and annotations
>  > (although obsolete!) are going to co-exist?
> 
> Building frontends that use annotations is actively discouraged.  If
> GDB/MI does not currently meet all your requirements then please contribute
> to its development.

I have to say, it would be a really bad idea to use the annotations.
Really bad. It's hard to do much of anything with what they provide.

However, GDB/MI will waste a lot of your time if your requirements
aren't meet through what it provides already. I'm just warning you.

Someone in the GDB development area basically decided to create GDB/MI 
as a nice protocol for GDB front ends. However, they didn't write a 
client to demostrate it's purposes. Each client reimplements all the 
work necessary to parse and interpret the protocol. Furthermore, every 
client wants something different and so has different expectations of 
what the interface should provide. Finally, if it doesn't do something 
you need, the standard answer is - do it yourself. Just for the icing 
on the cake, don't expect your patch to get reviewed for 6 months.

This is my experience. I have a bison parser that parses the GDB/MI
protocol, however, it only works with a bison version in CVS. Contact
me if you care.

Bob Rossi


  reply	other threads:[~2008-01-30  0:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29 22:37 Jain, Rohit
2008-01-29 23:40 ` Nick Roberts
2008-01-30  0:21   ` Bob Rossi [this message]
2008-01-30  2:20     ` Jain, Rohit
     [not found] <AF07433C464DDD48AB9D6A2E20BE3B0758C7D2@NA1-MAIL.mgc.mentorg.com>
     [not found] ` <AF07433C464DDD48AB9D6A2E20BE3B0758C82B@NA1-MAIL.mgc.mentorg.com>
2008-01-30  7:20   ` GDB Annotations : Support plan Vladimir Prus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080130002103.GC28482@brasko.net \
    --to=bob_rossi@cox.net \
    --cc=Rohit_Jain@mentor.com \
    --cc=gdb@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox