From: "Douglas Evans" <dje@google.com>
To: gdb@sourceware.org
Subject: inconsistency in thread naming
Date: Thu, 22 Nov 2007 00:23:00 -0000 [thread overview]
Message-ID: <e394668d0711211623v672e5f75seb72752a7456f000@mail.gmail.com> (raw)
When gdb switches to a particular thread it prints something like
[Switching to Thread 12345]
But the "thread" command takes thread numbers, e.g.
(gdb) thread 3
This inconsistency is a pain. Any objections to making things more
consistent? Any opinions on how this should work? A minimalist
solution might be to include the thread number (3 in the above
example) in the [Switching to ...] message. If there was a consistent
way to distinguish thread number(3) from thread id(12345) [apologies
if my terminology if wrong], then the "thread" command could take
either. E.g. one might support "thread 3" or "thread #12345". I
don't have a strong opinion on what to choose, I'm just thinking out
loud.
next reply other threads:[~2007-11-22 0:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 0:23 Douglas Evans [this message]
2007-11-26 19:21 ` Michael Snyder
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=e394668d0711211623v672e5f75seb72752a7456f000@mail.gmail.com \
--to=dje@google.com \
--cc=gdb@sourceware.org \
/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