public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
To: Michael Snyder <msnyder@sonic.net>
Cc: gdb@sources.redhat.com
Subject: Re: [RFC] named thread support
Date: Thu, 06 Oct 2005 17:23:00 -0000	[thread overview]
Message-ID: <1128619356.32443.22.camel@localhost.localdomain> (raw)
In-Reply-To: <003101c5ca89$66229580$677ba8c0@sonic.net>

Hi,


<snipped>

> 1) The generic part would be to add a name field to gdb's
> thread struct, with appropriate UI for manipulating and
> displaying it.  The "thread" and "thread apply" commands
> would be enhanced to accept a name as well as a number.

That sounds neat in terms of user interface. Associating meaningful
names with threads rather than viewing them in terms of thread id's
would enhance user experience.  

> 2) Target-specific part -- sends the gdb-selected names
> to the target, accepts target-selected names from the target
> and adds them to gdb thread database.
> 
> Part 1 could be used by everybody, independently of
> whether their target implements part 2.
> 
> Michael
> 
-- 
Ramana Radhakrishnan                                            
GNU Tools,
codito ergo sum (http://www.codito.com)

Office:+91 20 26051367 ext. 162  Mobile:+91 9890040009
                                                                        

  reply	other threads:[~2005-10-06 17:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-06 15:23 Michael Snyder
2005-10-06 17:23 ` Ramana Radhakrishnan [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 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=1128619356.32443.22.camel@localhost.localdomain \
    --to=ramana.radhakrishnan@codito.com \
    --cc=gdb@sources.redhat.com \
    --cc=msnyder@sonic.net \
    /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).