From: Eli Zaretskii <eliz@gnu.org>
To: Michael Snyder <msnyder@vmware.com>
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [RFC] info threads takes an argument
Date: Mon, 14 Feb 2011 20:40:00 -0000 [thread overview]
Message-ID: <83k4h2pe03.fsf@gnu.org> (raw)
In-Reply-To: <4D598863.1030507@vmware.com>
> Date: Mon, 14 Feb 2011 11:54:11 -0800
> From: Michael Snyder <msnyder@vmware.com>
>
> Documentation and NEWS also attached.
Thanks.
> + printf_filtered ("Thread %d has name '%s'\n", tp->num, tp->name);
No _() (here and elsewhere in this function)?
> *** Changes since GDB 7.2
>
> +* GDB has a new command: "thread find [regexp]".
> + It finds the thread id whose name, target id, or thread extra info
> + matches the given regular expression.
> +
This part is okay.
> +@item info threads @r{[}@var{ids}@r{]}
> +Display a summary of all threads currently in your program. Optional
> +argument @var{ids} means print information only about the specified
> +thread or threads.
We should say what is the syntax if @var{ids}. IIUC,
"@var{id}@dots{}" is a better way of expressing it (but still,
something should be said about the valid syntax, e.g. can I use
"23-32"?)
> +Search for and display thread ids whose name, target thread id, or
> +target extra info matches the supplied regular expression.
What you call "extra info" and "target thread id" is described under
different names just a few dozen lines above this text. Let's use a
consistent terminology, to avoid confusion, okay?
> +As well as being the complement to the @samp{thread name} command,
> +this command also allows you to identify a thread by its target thread
> +id. For instance, on Linux, the target thread id is the LWP id.
^^^^^
"GNU/Linux", right?
Okay with those changes.
next prev parent reply other threads:[~2011-02-14 20:18 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 [this message]
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
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=83k4h2pe03.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.com \
--cc=tromey@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