From: David Carlton <carlton@math.stanford.edu>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: obsoleting the annotate level 2 interface
Date: Tue, 21 Jan 2003 16:54:00 -0000 [thread overview]
Message-ID: <ro13cnmzbo7.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <vt265sjj6vi.fsf@zenia.red-bean.com>
On 21 Jan 2003 02:32:01 -0500, Jim Blandy <jimb@redhat.com> said:
> GDB seems to support two different ways of doing detailed annotations
> of its output for consumption by other programs: MI and 'set annotate
> 2'. I don't think annotation level 2 has many active users, if any at
> all. It pervades GDB's code. Would it make sense to put 'set
> annotate 2' on the path to obsolescence?
While we're at it, we should also obsolete gdb -epoch and the
'inspect' command. (See PR gdb/614.)
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-01-21 16:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 7:38 Jim Blandy
2003-01-21 16:15 ` Andrew Cagney
2003-01-21 16:54 ` David Carlton [this message]
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
2003-01-21 17:41 Michael Elizabeth Chastain
2003-01-21 20:25 ` David Carlton
2003-01-22 16:45 ` Andrew Cagney
2003-01-21 18:09 Michael Elizabeth Chastain
2003-01-22 7:56 ` Arnaud Charlet
[not found] <1043140716.4941.ezmlm@sources.redhat.com>
2003-01-21 19:03 ` Jim Ingham
2003-01-21 20:40 Michael Elizabeth Chastain
2003-02-04 1:45 Mike Mueller
2003-02-04 6:58 ` Andrew Cagney
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=ro13cnmzbo7.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--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