From: jtc@acorntoolworks.com (J.T. Conklin)
To: karen.osmond@gmail.com
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc][patch] Allow GDB to display user-defined thread names
Date: Thu, 04 Jun 2009 16:52:00 -0000 [thread overview]
Message-ID: <87tz2whrfy.fsf@orac.acorntoolworks.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0906041721010.32368@localhost.localdomain> (Karen Osmond's message of "Thu, 4 Jun 2009 17:43:14 +0100 (BST)")
Karen Osmond <karen.osmond@gmail.com> writes:
> So, if this is of interest, I'd like to spend the time to improve it but
> if anybody has time, it would be of great help if a gdb bod could
> volunteer to mentor me a bit... please? :)
Some systems have names that can be set programmatically w/
pthread_attr_setname() or pthread_attr_setname_np(). On such systems,
it might be useful for GDB's initial thread name be inherited from the
target.
--jtc
--
J.T. Conklin
next prev parent reply other threads:[~2009-06-04 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 16:43 Karen Osmond
2009-06-04 16:52 ` J.T. Conklin [this message]
2009-06-05 22:29 ` Tom Tromey
2009-06-05 22:43 ` Paul Pluzhnikov
2009-06-08 14:24 ` Karen Osmond
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=87tz2whrfy.fsf@orac.acorntoolworks.com \
--to=jtc@acorntoolworks.com \
--cc=gdb-patches@sourceware.org \
--cc=karen.osmond@gmail.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