From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Implement -thread-info.
Date: Fri, 14 Mar 2008 15:11:00 -0000 [thread overview]
Message-ID: <20080314151115.GB19288@caradoc.them.org> (raw)
In-Reply-To: <20080314150732.GA19288@caradoc.them.org>
On Fri, Mar 14, 2008 at 11:07:32AM -0400, Daniel Jacobowitz wrote:
> > I have realized that while the patch is mostly about MI, it also
> > touches generic code -- thread.c. Is that part of patch (attached again
> > for convenience) OK?
Oh, one other thing. I went back to look at Denis's patches. He made
-thread-info without an argument describe the current thread only.
Doesn't that seem useful, especially before we get notifications
completely hammered out? I do not see any other MI command that
reports the current thread.
So that would mean we needed -thread-list-all-threads back again.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-03-14 15:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 15:33 Vladimir Prus
2008-02-18 6:26 ` Nick Roberts
2008-02-18 7:38 ` Vladimir Prus
2008-02-18 21:45 ` Nick Roberts
2008-02-20 11:28 ` Vladimir Prus
2008-02-20 19:07 ` Eli Zaretskii
2008-02-20 19:38 ` Nick Roberts
2008-02-20 20:03 ` Vladimir Prus
2008-02-26 0:58 ` Nick Roberts
2008-02-26 1:21 ` Daniel Jacobowitz
2008-03-23 4:56 ` Nick Roberts
2008-03-23 7:38 ` Vladimir Prus
2008-03-23 16:22 ` Daniel Jacobowitz
2008-03-08 15:50 ` Vladimir Prus
2008-03-08 15:55 ` Vladimir Prus
2008-03-08 20:04 ` Nick Roberts
2008-03-10 7:59 ` Vladimir Prus
2008-03-10 9:13 ` Nick Roberts
2008-03-14 10:17 ` Vladimir Prus
2008-03-17 18:40 ` Michael Snyder
2008-03-14 15:08 ` Daniel Jacobowitz
2008-03-14 15:11 ` Daniel Jacobowitz [this message]
2008-03-14 17:04 ` Vladimir Prus
2008-03-14 18:04 ` Daniel Jacobowitz
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=20080314151115.GB19288@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
/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