Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Peter Kovacs <peter@kovax.org>
Cc: gdb@sources.redhat.com
Subject: Re: obsoleting annotate level 2
Date: Tue, 04 Feb 2003 17:16:00 -0000	[thread overview]
Message-ID: <15935.63082.332513.709831@localhost.redhat.com> (raw)
In-Reply-To: <20030204164141.GB2354@kovax.org>

Peter Kovacs writes:
 > On Tue, Feb 04, 2003 at 11:34:31AM -0500, Elena Zannoni wrote:
 > > If you have to keep supporting the old gdb, you will need to support
 > > two interfaces to gdb. Unless you are importing MI into
 > > 4.17.gnat.3.14p-1. If you have no control over 4.17.gnat.3.14p-1, and
 > > supporting that is your primary goal, I don't see what FSF gdb can do
 > > to correct that, ie I see two conflicting goals here.
 > 
 > Yes, we will continue to support --annotate=2 as well as the MI
 > interface.  I'm not sure why you see 2 conflicting goals.  Both
 > interfaces can be supported with no problems, after all we're not
 > interested in embedding our code into gdb itself.

OK, just wanted to point that out. They seem a conflicting in the
sense that one gdb is very old, and very different from the current
FSF one, but if you are ok with maintaining 2 interfaces, there is no
problem.

 > 
 > >  > As for the MI issues, I think we'd be willing to move over to the MI
 > >  > interface if and when it supports some of the readline style of input.
 > > 
 > > About readline, there was a conscious design decision to not provide
 > > it with MI, because the editing capabilities would be implemented at a
 > > different level, in the GUI console, not in gdb. With the interpreter
 > > changes the console becomes now a concrete possibility.  BTW, you may
 > > want to take a look at Apple's Project Builder, I don't know what
 > > level of editing they provided with their console.
 > 
 > I'm not sure I understand this.  How can the stand-alone GUI query gdb
 > for a list of symbol names?  For example, I type break m<tab>, and it
 > completes to "main".
 > 

there is a bug open against the lack of a 'completion' kind of
command in MI. See bug 953 in http://sources.redhat.com/gdb/bugs/

 > Unfortunately I don't have access to Apple's Project Builder.  Do they
 > offer the source to their debugger?
 > 

I think they do on their website. I don't have a pointer handy, sorry.

 > gdb's console is already quite capable, and many people are extremely
 > familiar with it.  I think it would be a shame if we have to completely
 > reimplement a console front-end to gdb.
 > 

insight does this too. Maybe that's another place to look.

elena


 > - Peter
 > 
 > -- 
 > Peter D. Kovacs <peter@kovax.org>


  parent reply	other threads:[~2003-02-04 17:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04 12:44 Bob Rossi
2003-02-04 15:49 ` Elena Zannoni
2003-02-04 16:12   ` Peter Kovacs
2003-02-04 16:30     ` Elena Zannoni
2003-02-04 16:37       ` Bob Rossi
2003-02-04 17:10         ` Elena Zannoni
2003-02-04 19:48           ` Jim Blandy
2003-02-04 21:22             ` Nick Roberts
2003-02-04 23:01               ` Andrew Cagney
2003-02-04 16:41       ` Peter Kovacs
2003-02-04 16:46         ` Peter Kovacs
2003-02-04 17:16         ` Elena Zannoni [this message]
2003-02-04 19:53 Mike Mueller
2003-02-05  6:57 ` Jim Blandy
2003-02-05 20:04   ` Bob Rossi

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=15935.63082.332513.709831@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=peter@kovax.org \
    /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