From: Nick Roberts <nick@nick.uklinux.net>
To: Andrew Cagney <cagney@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA (?) Annotate Level 3 patch
Date: Mon, 02 Feb 2004 22:09:00 -0000 [thread overview]
Message-ID: <16414.51421.622553.831432@nick.uklinux.net> (raw)
In-Reply-To: <4016A245.6030001@gnu.org>
> Can you post a log with/with-out this patch to illustrate what's
> happening. You're right - emacs should see "stopped" first but there
> might be a better long-term way to do this.
>
> I suspect this will mean playing with the print-stop-reason code.
Moving annotate_stopped to the start of normal_stop seems to do the right
thing. It might be bad practice, however, to break existing functionality so a
better solution might be to create a new annotation there - aargh! - called
stopping, say, instead. However, remember that I will have reduced my initial
set of 25 annotations to 14. They would be:
pre-prompt prompt post-prompt
commands overload-choice query
prompt-for-continue source starting
exited signalled signal
stopped
and stopping
And, of course, from time to time, I'm trying to get GDB/MI to work directly
with Emacs.
BTW I have seen that Vim developers are starting to use level 2 annotations
for their own front end to GDB.
( http://thread.gmane.org/gmane.editors.vim.devel/5024 )
Nick
next prev parent reply other threads:[~2004-02-02 22:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-05 20:10 Nick Roberts
2004-01-27 20:28 ` Andrew Cagney
2004-01-29 0:20 ` Annotations Nick Roberts
2004-02-02 22:09 ` Nick Roberts [this message]
2004-02-10 23:40 ` RFA (?) Annotate Level 3 patch Andrew Cagney
2004-02-12 21:53 ` Nick Roberts
2004-02-12 22:34 ` Bob Rossi
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=16414.51421.622553.831432@nick.uklinux.net \
--to=nick@nick.uklinux.net \
--cc=cagney@gnu.org \
--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