From: Andrew Cagney <ac131313@redhat.com>
To: Nick Roberts <nick@nick.uklinux.net>
Cc: gdb@sources.redhat.com
Subject: Re: GDB 6
Date: Sun, 11 May 2003 15:22:00 -0000 [thread overview]
Message-ID: <3EBE69AE.30001@redhat.com> (raw)
In-Reply-To: <16061.32163.69181.411133@nick.uklinux.net>
>> > What exactly do you mean here?
>> > Annotations Level 2 will stay in gdb for version 6.0?
>> > This would truly be a great thing.
>
>
>
>> It won't have been deleted (but it would continue to be on notice).
>
>
> Will GDB 6 have annotation level three? The patch that you posted (2003-03-11)
> doesn't appear to have been applied yet.
That's correct. I've got a small matter of the doco and testsuite to
resolve :-)
> I might have lost the plot a bit. I initially checked out interps-20030202-branch
> but, after some difficulty, I moved to HEAD and found that things like
>
> -interpreter-exec console cli-command
>
> and
>
> interpreter mi -<mi-command> <mi-args>
>
> were present there also. Am I in the right place?
Yes.
> In the past you have suggested that (in the fullness of time)
>
>
>> The events [annotations] remain (target changed, breakpoint created, ....).
>> The markups are removed (*-{begin,end})
There was some progress. Joel added a proper observer. Next is for the
breakpoint stuff to use that.
> I've got my head round variable objects and think that they might map on to
> alists and the Emacs speedbar quite well. This means I can avoid the
> annotations that mark up displayed expressions. However, the proposed patch
> also removed some event annotations e.g source, query. I would like these to
> stay. Here is a revised and reduced list of annotations that I think I could
> work with:
>
> 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
I'm not sure about frame begin. Things like frames-invalid are events
and they can stay (forever? ...).
Andrew
next prev parent reply other threads:[~2003-05-11 15:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 22:35 Nick Roberts
2003-05-11 15:22 ` Andrew Cagney [this message]
2003-05-12 18:57 ` Nick Roberts
2003-05-11 22:00 ` Andrew Cagney
2003-05-12 19:29 ` Bob Rossi
2003-05-13 17:47 ` Nick Roberts
2003-05-12 19:36 ` Bob Rossi
2003-05-13 17:47 ` Nick Roberts
-- strict thread matches above, loose matches on Subject: below --
2003-05-09 18:17 Michael Elizabeth Chastain
2003-05-09 20:25 ` Andrew Cagney
2003-05-09 16:58 Andrew Cagney
2003-05-09 17:12 ` Daniel Jacobowitz
2003-05-09 17:41 ` Elena Zannoni
2003-05-09 18:05 ` Bob Rossi
2003-05-09 20:21 ` 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=3EBE69AE.30001@redhat.com \
--to=ac131313@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).