From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: scott.harrison@tandberg.com, gdb-patches@sourceware.org
Subject: Re: New feature: allow thread command to take a LWPID.
Date: Fri, 05 Feb 2010 03:28:00 -0000 [thread overview]
Message-ID: <20100205032801.GD2715@adacore.com> (raw)
In-Reply-To: <m3k4usinos.fsf@fleche.redhat.com>
> I am not super fond of the syntax. I don't have a better suggestion
> though :-(
I agree about the syntax. How about using a command "switch".
For instance:
(gdb) thread THREAD_NO
(gdb) thread /l LWP
We could even think of adding:
(gdb) thread /t TID
(for the platforms that use the tid rather than the lwp).
--
Joel
next prev parent reply other threads:[~2010-02-05 3:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-04 11:35 scott.harrison
2010-02-04 23:30 ` Tom Tromey
2010-02-05 3:28 ` Joel Brobecker [this message]
2010-02-05 9:40 ` scott.harrison
2010-02-05 10:07 ` Joel Brobecker
2010-02-05 10:53 ` Andreas Schwab
2010-02-05 11:49 ` Joel Brobecker
2010-02-05 16:04 ` Tom Tromey
2010-02-08 6:13 ` Joel Brobecker
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=20100205032801.GD2715@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=scott.harrison@tandberg.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