From: Nick Roberts <nick@nick.uklinux.net>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com, bob_rossi@cox.net
Subject: [rfc] Annotation level THREE
Date: Fri, 14 Mar 2003 00:08:00 -0000 [thread overview]
Message-ID: <15985.7336.23998.590592@nick.uklinux.net> (raw)
In-Reply-To: <3E6E7326.3020906@redhat.com>
> To follow through a discussion on gdb@ this patch adds annotation level
> three to the GDB sources.
> Annotation level three:
> - keeps the event notifications from annotation level two
> - removes all the output markups
I don't really follow this. It looks like level three annotations will have
a lot of the annotations missing. To currently work gdb-ui.el needs:
frames-invalid
breakpoints-invalid
pre-prompt
prompt
commands
overload-choice
query
prompt-for-continue
post-prompt
source
starting
exited
signalled
signal
breakpoint
watchpoint
frame-begin
stopped
display-begin
display-end
display-number-end
array-section-begin
array-section-end
field-begin
field-end
It needn't use frames-invalid and breakpoints-invalid which are repeatedly
generated during a run and possibly other selected ones could go. However,
some appear to be essential e.g display-begin as the MI equivalent,
-display-insert, isn't implemented and I don't know how to make use of
variable objects.
Nick
next prev parent reply other threads:[~2003-03-14 0:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 23:37 Andrew Cagney
2003-03-12 18:54 ` David Carlton
2003-03-12 19:04 ` Andrew Cagney
2003-03-14 0:08 ` Nick Roberts [this message]
2003-03-17 0:23 ` Andrew Cagney
2003-03-17 20:07 ` Nick Roberts
2003-03-17 20:38 ` Andrew Cagney
2003-03-18 10:31 ` Nick Roberts
2003-03-18 15:29 ` Andrew Cagney
2003-03-18 16:00 ` Andrew Cagney
2003-03-18 20:17 ` Bob Rossi
2003-03-12 6:09 Michael Elizabeth Chastain
2003-03-12 14:50 ` Andrew Cagney
2003-03-12 14:56 ` Daniel Jacobowitz
2003-03-12 17:04 ` David Carlton
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=15985.7336.23998.590592@nick.uklinux.net \
--to=nick@nick.uklinux.net \
--cc=ac131313@redhat.com \
--cc=bob_rossi@cox.net \
--cc=gdb-patches@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