Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches\@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFC] info threads takes an argument
Date: Mon, 21 Feb 2011 18:45:00 -0000	[thread overview]
Message-ID: <m3mxlpp6t4.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4D5AEDA7.1000405@vmware.com> (Michael Snyder's message of "Tue,	15 Feb 2011 13:18:31 -0800")

>>>>> "Michael" == Michael Snyder <msnyder@vmware.com> writes:

Tom> Matching both the ID and the target PID means that using numbers here
Tom> will be over-eager.  Why match the ID?  "info thread ID" seems good
Tom> enough.

Michael> "info thread" will only match the gdb thread id (small counting
Michael> integer).  "thread find" will match the PID.

Yes, sorry -- I misunderstood the text and did not read the
corresponding part of the code.

Tom


      parent reply	other threads:[~2011-02-21 18:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-11  1:52 Michael Snyder
2011-02-11  6:09 ` Joel Brobecker
2011-02-11 19:23   ` Michael Snyder
2011-02-11 21:14     ` Tom Tromey
     [not found]       ` <4D55B1ED.5020808@vmware.com>
     [not found]         ` <m3k4h2e6xu.fsf@fleche.redhat.com>
2011-02-14 20:03           ` Michael Snyder
2011-02-14 20:40             ` Eli Zaretskii
2011-02-15 19:58             ` Tom Tromey
2011-02-15 21:44               ` Michael Snyder
2011-02-16 11:58                 ` Pedro Alves
2011-02-16 18:47                   ` Michael Snyder
2011-02-17 16:57                     ` Jan Kratochvil
2011-02-17 19:12                       ` Michael Snyder
2011-02-17 20:11                       ` Michael Snyder
2011-02-17 21:22                         ` Jan Kratochvil
2011-02-21 18:45                 ` Tom Tromey [this message]

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=m3mxlpp6t4.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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