Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Hooks still needed for annotations
Date: Fri, 15 Jul 2005 00:03:00 -0000	[thread overview]
Message-ID: <20050715000326.GC21620@nevyn.them.org> (raw)
In-Reply-To: <20050706150333.GB17788@white>

On Wed, Jul 06, 2005 at 11:03:33AM -0400, Bob Rossi wrote:
> On Sun, Jul 03, 2005 at 12:39:16PM -0400, Daniel Jacobowitz wrote:
> > On Wed, Jun 15, 2005 at 06:57:59PM -0400, Bob Rossi wrote:
> > > >  > >  > Do you already use level 3, or could we simply just start stripping down
> > > >  > >  > level 2?
> > 
> > The point of introducing level 3 - a stripped down version of level 2 -
> > was to transition clients to using it and then discard level 2, instead
> > of having to find everyone using annotations and work out whether we
> > broke them every time someone wants to strip something out of level 2. 
> > When everyone we care about is happy with level 3, we can kill level 2.
> > 
> > Bob, sometimes I feel like you pick very strange things to label as
> > "hard".  What's hard about autodetecting the availability of annotate
> > level 3?  Or even doing it based on version number?
> 
> I just simply can't stand the thought of starting up GDB several times
> to determine what the correct protocol the FE should use. This
> doesn't seem necessary.

But it's _simpler_ than any of this complicated handshaking, or even
the revised -i option you suggested below.  Just start GDB with the
interface you want it to use.  If it doesn't recognize it, it will
quickly and clearly tell you so.

drow@nevyn:~% gdb -i=mi4
Interpreter `mi4' unrecognized

-- 
Daniel Jacobowitz
CodeSourcery, LLC


      reply	other threads:[~2005-07-15  0:03 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-01  7:15 Nick Roberts
2005-06-01 11:30 ` Bob Rossi
2005-06-01 21:31   ` Nick Roberts
2005-06-03 19:09     ` Daniel Jacobowitz
2005-06-03 22:35       ` Nick Roberts
2005-06-03 23:59         ` Daniel Jacobowitz
2005-06-04  3:19           ` Nick Roberts
2005-07-03 17:03             ` Daniel Jacobowitz
2005-07-03 22:13               ` Nick Roberts
2005-07-03 22:44                 ` Daniel Jacobowitz
2005-06-04 13:02           ` Bob Rossi
2005-06-13  3:14             ` Daniel Jacobowitz
2005-06-15 15:52               ` Bob Rossi
2005-06-15 16:07                 ` Daniel Jacobowitz
2005-06-15 16:31                   ` Bob Rossi
2005-07-03 16:45                     ` Daniel Jacobowitz
2005-06-15 23:07                 ` Nick Roberts
2005-06-15 23:29                   ` Bob Rossi
2005-07-01  0:21               ` Bob Rossi
2005-07-01  1:18                 ` Nick Roberts
2005-06-06 21:57           ` Nick Roberts
2005-06-10  2:26             ` Bob Rossi
2005-06-10  3:25               ` Nick Roberts
2005-06-15 15:24                 ` Bob Rossi
2005-06-15 21:38                   ` Nick Roberts
2005-06-15 22:58                     ` Bob Rossi
2005-07-03 16:39                       ` Daniel Jacobowitz
2005-07-06 15:03                         ` Bob Rossi
2005-07-15  0:03                           ` Daniel Jacobowitz [this message]

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=20050715000326.GC21620@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    /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