From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC] Implement =thread-selected notification.
Date: Sat, 16 Aug 2008 20:19:00 -0000 [thread overview]
Message-ID: <20080816201842.GC9401@caradoc.them.org> (raw)
In-Reply-To: <200808131640.16054.vladimir@codesourcery.com>
On Wed, Aug 13, 2008 at 04:40:15PM +0400, Vladimir Prus wrote:
>
> I've previously posted a spec of how thread management should work
> between MI frontend and GDB. Parts of that spec -- namely --thread
> and --frame options were implemented. This patch adds =thread-selected
> notification, so that I go ahead and convert that spec into manual
> section.
>
> I went with Dan's suggestion of reporting the change if we end up
> with different thread after MI command is done -- which means we don't
> have to carefully suppress notifications due to "internal" thread switches.
>
> Only doc changes need formal approval; feedback on other bits is appreciated.
Looks fine to me.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2008-08-16 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 12:41 Vladimir Prus
2008-08-13 18:30 ` Eli Zaretskii
2008-08-16 20:19 ` Daniel Jacobowitz [this message]
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=20080816201842.GC9401@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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