From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Nick Roberts <nickrob@snap.net.nz>, Daniel Jacobowitz <drow@false.org>
Subject: Re: [PATCH:MI] Event notification
Date: Tue, 10 Jun 2008 07:02:00 -0000 [thread overview]
Message-ID: <200806100525.25937.pedro@codesourcery.com> (raw)
In-Reply-To: <18509.60583.390202.377448@kahikatea.snap.net.nz>
A Tuesday 10 June 2008 03:53:27, Nick Roberts wrote:
> Perhaps the answer then is to put notification explicitly in each CLI and
> MI command (as I've proposed for thread_command and mi_cmd_thread_select).
I'm working on a patch that's needed for non-stop that splits the notion of
user/frontend selected thread and frame, from the internally
selected thread and frame. With it in place, it should be easy to place an
observer call in the function called to record the current thread and frame.
--
Pedro Alves
next prev parent reply other threads:[~2008-06-10 4:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 0:42 Nick Roberts
2008-05-01 18:57 ` Daniel Jacobowitz
2008-06-10 2:20 ` Nick Roberts
2008-06-10 2:54 ` Daniel Jacobowitz
2008-06-10 4:25 ` Nick Roberts
2008-06-10 7:02 ` Pedro Alves [this message]
2008-05-04 12:19 ` Vladimir Prus
2008-05-04 21:34 ` Daniel Jacobowitz
2008-05-04 23:19 ` Nick Roberts
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=200806100525.25937.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=nickrob@snap.net.nz \
/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