From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: kewarken@qnx.com, gdb@sources.redhat.com
Subject: Re: [RFC] named thread support
Date: Sun, 09 Oct 2005 20:35:00 -0000 [thread overview]
Message-ID: <200510092034.j99KYffG008327@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20051006012139.GA21277@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 5 Oct 2005 21:21:39 -0400)
> Date: Wed, 5 Oct 2005 21:21:39 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> On Tue, Oct 04, 2005 at 12:40:22PM -0400, Kris Warkentin wrote:
> > Would it be of interest to have a generic 'set threadname <tid> <name>'
> > that called a target_set_threadname()? I ask because we're implementing
> > named threads in our kernel but I don't know if many other systems
> > support this. I can always add it to our backend but if someone else
> > might use it in the future, I can make it general.
>
> So by named thread support, you mean that the application can register
> the name of the thread with the kernel? And you want GDB to be able to
> set thread names?
>
> I recommend doing this in your backend, since I don't know any other
> gdb-supported system with a similar feature.
I think HP-UX allows you to do the same thing, and many user-space
threads implementations allow you to do something very similar.
Mark
next prev parent reply other threads:[~2005-10-09 20:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 16:40 Kris Warkentin
2005-10-06 1:21 ` Daniel Jacobowitz
2005-10-09 20:35 ` Mark Kettenis [this message]
2005-10-09 20:40 ` Daniel Jacobowitz
2005-10-06 18:30 ` Stan Shebs
2005-10-07 15:14 ` Daniel Jacobowitz
2005-10-06 12:34 Kris Warkentin
2005-10-06 15:23 Michael Snyder
2005-10-06 17:23 ` Ramana Radhakrishnan
2005-10-06 17:40 Kris Warkentin
2005-10-07 16:53 Kris Warkentin
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=200510092034.j99KYffG008327@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=kewarken@qnx.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).