From: Vladimir Prus <vladimir@codesourcery.com>
To: Pawel Piech <pawel.piech@windriver.com>, gdb@sources.redhat.com
Subject: Re: non-stop and current thread exiting
Date: Thu, 05 Jun 2008 05:50:00 -0000 [thread overview]
Message-ID: <200806050950.19833.vladimir@codesourcery.com> (raw)
In-Reply-To: <4846F753.7060204@windriver.com>
On Thursday 05 June 2008 00:13:07 you wrote:
> As far as I remember -thread-info displays information
> about a single thread, though I don't think it's implemented.
> -thread-list-all-threads which is supposed to be equivalent to info
> threads, could show exited threads and let the UI filter them out.
> However -thread-list-ids, which is actually implemented, only lists IDs,
> so there's no way for the UI to tell which ones are live.
-thread-info is implemented in CVS HEAD, and can either report all threads
(when used without a parameter), or a specific thread. There's also a patch
to make it report, for each thread, if it's running or not.
-thread-list-all-threads will not be implemented, in light of current
-thread-info behaviour.
-thread-list-ids is a historical artefact, using it is strictly inferiour
to -thread-info, and the frontend should first probe -thread-info and use
-thread-list-ids as a fallback only.
- Volodya
next prev parent reply other threads:[~2008-06-05 5:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 21:54 Pedro Alves
2008-06-03 22:01 ` Joel Brobecker
2008-06-04 0:53 ` Marc Khouzam
2008-06-04 4:57 ` Vladimir Prus
2008-06-05 13:18 ` Marc Khouzam
2008-06-05 13:27 ` Vladimir Prus
2008-06-05 21:23 ` Pawel Piech
2008-06-04 15:10 ` Pawel Piech
2008-06-04 17:08 ` Pedro Alves
2008-06-04 17:38 ` Vladimir Prus
[not found] ` <4846F753.7060204@windriver.com>
2008-06-05 5:50 ` Vladimir Prus [this message]
2008-06-05 21:23 ` Pawel Piech
2008-06-05 23:48 ` Pawel Piech
2008-06-10 15:14 ` Pedro Alves
2008-06-04 17:34 ` Michael Snyder
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=200806050950.19833.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=gdb@sources.redhat.com \
--cc=pawel.piech@windriver.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