From: Kris Warkentin <KEWarken@qnx.com>
To: 'Daniel Jacobowitz' <drow@false.org>, Kris Warkentin <KEWarken@qnx.com>
Cc: GDB <gdb@sources.redhat.com>
Subject: RE: [RFC] named thread support
Date: Thu, 06 Oct 2005 12:34:00 -0000 [thread overview]
Message-ID: <3518719F06577C4F85DA618E3C37AB9101CFC7E0@nimbus.ott.qnx.com> (raw)
> 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?
Exactly. When I implemented the reading of the names from the target it
occurred to me that I could set names as well. It's not a super useful or
high priority item but it's easy and fun so I thought I'd do it anyway. ;-)
> I recommend doing this in your backend, since I don't know any other
> gdb-supported system with a similar feature.
No problem.
cheers,
Kris
next reply other threads:[~2005-10-06 12:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 12:34 Kris Warkentin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-07 16:53 Kris Warkentin
2005-10-06 17:40 Kris Warkentin
2005-10-06 15:23 Michael Snyder
2005-10-06 17:23 ` Ramana Radhakrishnan
2005-10-04 16:40 Kris Warkentin
2005-10-06 1:21 ` Daniel Jacobowitz
2005-10-09 20:35 ` Mark Kettenis
2005-10-09 20:40 ` Daniel Jacobowitz
2005-10-06 18:30 ` Stan Shebs
2005-10-07 15:14 ` 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=3518719F06577C4F85DA618E3C37AB9101CFC7E0@nimbus.ott.qnx.com \
--to=kewarken@qnx.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.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).