From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: improved thread id reporting
Date: Mon, 06 Apr 2009 07:39:00 -0000 [thread overview]
Message-ID: <20090406033300.GA31715@caradoc.them.org> (raw)
In-Reply-To: <e394668d0904051336p56704603of8c9c31742dc04e6@mail.gmail.com>
On Sun, Apr 05, 2009 at 01:36:06PM -0700, Doug Evans wrote:
> Attached is a simplistic patch to help illustrate the challenge.
>
> Here is an example session that prints from/to and the thread number
> in "[New ...", "[Switching ...", etc. messages.
> I can think of two issues with the patch:
> 1) Printing "[tT]hread" twice in one line is a bit annoying.
> 2) Spreading from/to over two lines is a bit annoying.
What do you think of this? On the theory that you can go look up
thread #2, either in 'info threads' or in a previous notification:
[Switching from thread #2 to thread #3, Thread 0x41001960 (LWP 14407)]
Or, migrating the "Thread" out:
[Switching from thread #2 to thread #3, 0x41001960 (LWP 14407)]
But that might be tricky with multi-process, some ptid_t's are not
threads.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-04-06 3:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 19:06 Doug Evans
2009-04-04 19:07 ` Mark Kettenis
2009-04-04 20:40 ` Daniel Jacobowitz
2009-04-04 21:21 ` Eli Zaretskii
2009-04-04 22:17 ` Daniel Jacobowitz
2009-04-05 1:11 ` Doug Evans
2009-04-05 3:42 ` Eli Zaretskii
2009-04-05 3:48 ` Daniel Jacobowitz
2009-04-05 7:19 ` Paul Pluzhnikov
2009-04-05 18:50 ` Eli Zaretskii
2009-04-05 20:11 ` Paul Pluzhnikov
2009-04-05 20:36 ` Eli Zaretskii
2009-04-04 22:35 ` Doug Evans
2009-04-06 2:58 ` Doug Evans
2009-04-06 3:33 ` Eli Zaretskii
2009-04-06 15:36 ` Mark Kettenis
2009-04-06 20:21 ` Eli Zaretskii
2009-04-06 7:39 ` Daniel Jacobowitz [this message]
2009-04-06 21:21 ` Eli Zaretskii
2009-05-08 5:43 ` Doug Evans
2009-04-06 20:20 ` Tom Tromey
2009-04-06 20:20 ` Eli Zaretskii
2009-04-06 22:15 ` Tom Tromey
2009-04-07 15:18 ` Doug Evans
2009-04-04 22:24 ` Doug Evans
2009-04-05 3:13 ` Daniel Jacobowitz
2009-04-05 9:16 ` Mark Kettenis
2009-04-05 18:23 ` Eli Zaretskii
2009-04-05 19:22 ` Doug Evans
2009-04-04 19:20 ` Thiago Jung Bauermann
2009-04-04 19:21 ` Eli Zaretskii
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=20090406033300.GA31715@caradoc.them.org \
--to=drow@false.org \
--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