From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb@sources.redhat.com, jimb@redhat.com
Subject: Re: obsoleting the annotate level 2 interface
Date: Tue, 21 Jan 2003 17:41:00 -0000 [thread overview]
Message-ID: <200301211741.h0LHfp308677@duracef.shout.net> (raw)
Jim Blandy writes:
> If folks agree that annotate level 2 should go, we could:
> - announce that annotate level 2 will be disabled in the release after
> next;
> - in that release, disable the code, but leave it there, to see if
> anyone complains, and whether they can be persuaded to switch to MI;
> and
> - in the release after that, if all goes well, remove the code to
> support annotation level 2.
According to the NEWS file in gdb 5.1, the annotation interface
is deprecated. So I say, go for it!
There is one PR open against annotation level 2: pr gdb/785. I think we
can quash it if we remove annotation level 2. I sent mail to the
submitter, rros7605@postoffice.uri.edu, about other matter (pr gdb/786)
on 2003-01-01 and haven't heard back from them, so they probably don't
care. And if we remove annotation level 2, then we don't care.
gdb.c++/annota2.exp reports two KFAIL's which are unrelated to
annotation. One KFAIL is about a hardware watchpoint that triggers on
the first instruction after resuming a breakpoint. The other is about
sending a ^C and then immediately reading from gdb (I suspect there is a
race condition here but I'm not sure). Actually it would be good to
move those tests to a different test script right now, because it's such
a pain to work with an annotation-enabled test script.
I've made a note in my TODO list to do that.
> Personally, I'd like to see Emacs switch from annotation level 1 to
> MI, too; then we could get rid of annotation altogether. But I think
> it makes sense to tackle level 2 first, since I don't think it has
> many users (if any).
emacs invokes gdb with "gdb -fullname" so it's just our gdb code which
maps that to "annotate level 1". We can continue to do the same
behavior and just call it the "fullname" flag instead of the
"annotation" flag.
It looks a bit hard to remove the behavior, because lisp/gud.el
interacts with many different debuggers. I suppose it would be nice to
have a new emacs gdb interface which takes full advantage of MI, but
that would not make lisp/gud.el obsolete, so the "-fullname" behavior
would not be obsolete.
Michael C
next reply other threads:[~2003-01-21 17:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 17:41 Michael Elizabeth Chastain [this message]
2003-01-21 20:25 ` David Carlton
2003-01-22 16:45 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2003-02-04 1:45 Mike Mueller
2003-02-04 6:58 ` Andrew Cagney
2003-01-21 20:40 Michael Elizabeth Chastain
[not found] <1043140716.4941.ezmlm@sources.redhat.com>
2003-01-21 19:03 ` Jim Ingham
2003-01-21 18:09 Michael Elizabeth Chastain
2003-01-22 7:56 ` Arnaud Charlet
2003-01-21 7:38 Jim Blandy
2003-01-21 16:15 ` Andrew Cagney
2003-01-21 16:54 ` David Carlton
2003-01-21 19:04 ` Eli Zaretskii
2003-01-22 8:37 ` Pierre Muller
2003-01-22 15:06 ` Elena Zannoni
[not found] ` <15917.39229.935851.920452@nick.uklinux.net>
2003-01-28 20:51 ` Jim Blandy
2003-01-29 1:41 ` Nick Roberts
2003-01-29 5:37 ` Andrew Cagney
2003-01-29 5:40 ` Andrew Cagney
2003-01-29 21:58 ` Jim Blandy
2003-01-29 22:00 ` Arnaud Charlet
2003-01-29 22:50 ` Andrew Cagney
2003-01-29 21:52 ` Jim Blandy
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=200301211741.h0LHfp308677@duracef.shout.net \
--to=mec@shout.net \
--cc=gdb@sources.redhat.com \
--cc=jimb@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