public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/8618] Extract the thread name
Date: Tue, 11 May 2010 09:23:00 -0000 [thread overview]
Message-ID: <20100511092312.6624.qmail@sourceware.org> (raw)
In-Reply-To: <20040114185800.8618.alain@qnx.com>
------- Additional Comments From mjw at redhat dot com 2010-05-11 09:23 -------
This idea was also mentioned here:
http://0pointer.de/blog/projects/name-your-threads.html
"So, now go, if you have a project which involves a lot of threads, name them
all individually, and make it easier to debug them. What's missing now, of
course, is that gdb learns this and shows the comm name when doing info threads."
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |mjw at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=8618
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next parent reply other threads:[~2010-05-11 9:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040114185800.8618.alain@qnx.com>
2010-05-11 9:23 ` mjw at redhat dot com [this message]
2010-05-11 9:31 ` mjw at redhat dot com
2010-05-11 10:40 ` scottt dot tw at gmail dot com
2010-05-17 23:00 ` kinetik at flim dot org
2010-05-24 4:52 ` ppluzhnikov at google dot com
2010-07-12 19:18 ` jan dot kratochvil at redhat dot com
2010-07-31 16:03 ` jan dot kratochvil at redhat dot com
[not found] <bug-8618-4717@http.sourceware.org/bugzilla/>
2011-01-11 18:28 ` tromey at redhat dot com
2011-01-19 17:22 ` cvs-commit at gcc dot gnu.org
2011-01-19 17:26 ` tromey at redhat dot com
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=20100511092312.6624.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).