From: Nick Roberts <nick@nick.uklinux.net>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: [Various] obsoleting the annotate level 2 interface
Date: Fri, 31 Jan 2003 22:33:00 -0000 [thread overview]
Message-ID: <15930.63739.197712.283245@nick.uklinux.net> (raw)
In-Reply-To: <15930.58372.75272.21296@localhost.redhat.com>
> > Ah, don't be fooled by the current online documentation... ;-)
> I don't understand. The on line doc is up to date, it is not
> lying.
Sorry, it was just a cheeky paraphrase of something Andrew Cagney said earlier.
Trying to be more helpful, the documentation says that -break-info has not
been implemented yet but it seems to work even on my version of gdb
(GNU gdb 20010813 (MI_OUT)). If -break-info does work, then presumably
-break-list is not needed.
> Those commands have not been implememted. We have gone through
> 3 projects (one internal to Cygnus, eclipse, and the apple ui) and
> none of those missing commands was obviously a show stopper.
gdb-ui.el currently uses the CLI equivalent of:
-display-delete
-display-disable
-display-enable
-display-insert
-display-list
although enable/disable probably aren't necessary. How do the other projects
display variables ?
> Of course those are *new* GUIs and they can be less functional. Emacs
> cannot go backwards because some commands are missing.
I imagine most modern GUIs are currently more functional than the one that I
have provided for Emacs. It is the context of Emacs where I think the value
of gdb-ui.el lies.
> for instance, does emacs have a window that shows the threads of the
> inferior?
I've done nothing about threads, partly because different operating systems
seem to treat them differently and partly from my lack of understanding of
them.
> But it is not hard to implement them. These are fairly simple, almost
> wrappers.
I agree there's no point of implementing them for the sake of it. If the
existing commands work for the three projects you mention, then they should
also work for Emacs.
That just leaves the question of the console, which Andrew covers in his
e-mail.
Nick
next prev parent reply other threads:[~2003-01-31 22:33 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
[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 [this message]
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=15930.63739.197712.283245@nick.uklinux.net \
--to=nick@nick.uklinux.net \
--cc=ezannoni@redhat.com \
--cc=gdb@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