public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Kris Warkentin <KEWarken@qnx.com>
To: 'Daniel Jacobowitz' <drow@false.org>, Stan Shebs <shebs@apple.com>
Cc: Kris Warkentin <KEWarken@qnx.com>, GDB <gdb@sources.redhat.com>
Subject: RE: [RFC] named thread support
Date: Fri, 07 Oct 2005 16:53:00 -0000	[thread overview]
Message-ID: <3518719F06577C4F85DA618E3C37AB9101CFC7EE@nimbus.ott.qnx.com> (raw)

> -----Original Message-----
> From: Daniel Jacobowitz [mailto:drow@false.org]
> On Thu, Oct 06, 2005 at 11:30:22AM -0700, Stan Shebs wrote:
> > 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.
> > 
> > This actually was on the wishlist ages ago, ca 1998 or so I think,
> > probably connected with eCos plans. Even a target that didn't
> > support named threads could still make use of the generic 
> capability,
> > for instance via setup scripts - break at a place known unique to a
> > particular thread, get tid, name it, then user and other scripts can
> > reliably use the name.
> 
> I find this much more interesting than the way I interpreted Kris's
> original question - I don't think many targets will be interested in
> propogating the thread name to the target, but more will be interested
> in retrieving the thread name from the target, and all will be
> interested in user-defined names in the interface.  Let's do it! :-)

Cool.  We're putting another person on our gdb team (Jeff Baker who you
might know from the binutils mailing list) so he and I will work on this.
Sounds like a fun project.

cheers,

Kris

             reply	other threads:[~2005-10-07 16:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-07 16:53 Kris Warkentin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-10-06 17:40 Kris Warkentin
2005-10-06 15:23 Michael Snyder
2005-10-06 17:23 ` Ramana Radhakrishnan
2005-10-06 12:34 Kris Warkentin
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=3518719F06577C4F85DA618E3C37AB9101CFC7EE@nimbus.ott.qnx.com \
    --to=kewarken@qnx.com \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=shebs@apple.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).