Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Elena Zannoni <ezannoni@redhat.com>,
	Nick Roberts <nick@nick.uklinux.net>
Cc: gdb@sources.redhat.com
Subject: Re: [Various] obsoleting the annotate level 2 interface
Date: Fri, 31 Jan 2003 21:10:00 -0000	[thread overview]
Message-ID: <3E3AE629.3080104@redhat.com> (raw)
In-Reply-To: <15930.58372.75272.21296@localhost.redhat.com>


> As far as the interpreter stuff, there are up to date patches I
> posted, but I didn't have time to commit. They might need a day or so
> of work & testing. If somebody feels lucky....

Do I need a life?  I'll sort those out this weekend (and resist the 
temptation to pick at another loose thread) and get them into current GDB.

This will mean that the pressure is on to quickly spin out a GDB 5.4 
containing the updates.

Nick,

These patches, among other things, add the new CLI command 
`interpreter'.  This command lets you do things like:

(gdb) interpreter mi -<mi-command> <mi-args>
.... mi output ...
(gdb)

and will allow EMACS to query GDB using the MI (breakpoint list, frame 
backtrace, ...) with out requiring a complete rewrite.

Assuming that the level-two annotations are largely needed for the CLI 
version of those, this in turn will make it possible for EMACS to 
migrate at least partially to MI and at the same time drop the only just 
added level-two annotations requirement.

Long term, it would be good if EMACS used the -mi interpreter by 
default, but I don't see that as an absolute requirement.

RMS has indicated that if I and you agree to finish the MI support that 
Emacs needs, and convert Emacs to use it, in a short time (say, three 
months), he would go along with that plan.

I do manage to cover the MI side this weekend, can you, with some help 
from a few other GDB / EMACS hackers, cover the EMACS side?

Andrew



  reply	other threads:[~2003-01-31 21:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-31 20:14 Nick Roberts
2003-01-31 20:56 ` Elena Zannoni
2003-01-31 21:10   ` Andrew Cagney [this message]
     [not found]     ` <15931.6572.456534.588251@nick.uklinux.net>
     [not found]       ` <15931.8581.923838.921739@localhost.redhat.com>
2003-02-01 16:16         ` Nick Roberts
2003-01-31 22:33   ` Nick Roberts
2003-02-01  4:13   ` Jim Blandy
     [not found] <1044050405.3227.ezmlm@sources.redhat.com>
2003-02-01  0:43 ` Jim Ingham
  -- strict thread matches above, loose matches on Subject: below --
2003-01-28 20:05 Jim Blandy
2003-01-28 20:36 ` Andrew Cagney
2003-01-29  6:14   ` Eli Zaretskii
2003-01-29 21:56     ` Jim Blandy
2003-01-28 22:29 ` Arnaud Charlet
2003-01-29  5:38   ` Andrew Cagney
2003-01-29  8:55     ` Arnaud Charlet
2003-01-29 15:19       ` Andrew Cagney
2003-01-29 15:31         ` Arnaud Charlet
2003-01-29 15:43           ` Andrew Cagney
2003-01-29 15:51             ` Arnaud Charlet
2003-01-29 15:55               ` Christopher Faylor
2003-01-29 16:01                 ` Arnaud Charlet
2003-01-29 16:19                   ` Andrew Cagney
2003-01-29 16:34                     ` Arnaud Charlet
2003-01-29 17:16                       ` Andrew Cagney
2003-01-29 19:03                       ` Tom Tromey
2003-01-29 22:38                         ` Jim Blandy
2003-01-29 17:19         ` Eli Zaretskii

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=3E3AE629.3080104@redhat.com \
    --to=ac131313@redhat.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=nick@nick.uklinux.net \
    /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