From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: Jonny Grant <jg@jguk.org>, gdb@sourceware.org
Subject: Re: gdb show thread names
Date: Sat, 13 Jun 2020 14:47:23 +0200 [thread overview]
Message-ID: <5e3daadd5ee841b6f6d4ba4948849fa53ffe2107.camel@skynet.be> (raw)
In-Reply-To: <030e3603-12ab-d3cb-afe7-2628acbc18e3@jguk.org>
One year ago, I started a patch to add Ada task names and thread names.
At the end, the patch for Ada task name went in, but for the thread
names, there were still some work to do e.g. it was unclear how to
properly give the thread name in some cases and/or
have a consistent presentation of the thread name.
The (partial) patch was giving a behaviour so that we e.g. get:
[New Thread 0x7ffff701b700 (LWP 13891) "sleepers"]
[Switching to thread 2 (Thread 0x7ffff781c700 (LWP 13890) "sleepers")]
instead of:
[New Thread 0x7ffff701b700 (LWP 13918)]
[Switching to thread 2 (Thread 0x7ffff781c700 (LWP 13917))]
Philippe
On Sat, 2020-06-13 at 01:16 +0100, Jonny Grant wrote:
> Hello
> Just wondering if gdb could show the thread names as they are created and deleted?
>
>
> [Thread 0x7fff695e9700 (LWP 3580240) exited]
> [New Thread 0x7fff98ff9700 (LWP 3580609)]
>
> $ cat /proc/3580609/comm
> ThreadPoolForeg
>
> Could be a race condition, if GDB showed the name, before it was renamed by the application, but still pretty useful to see the names.
>
> If I break, and type "info thread" I can see those still created.
>
> Jonny
next prev parent reply other threads:[~2020-06-13 12:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 0:16 Jonny Grant
2020-06-13 12:47 ` Philippe Waroquiers [this message]
2020-06-13 22:22 ` Jonny Grant
2020-06-14 14:22 ` Philippe Waroquiers
2020-06-15 15:51 ` Pedro Alves
2020-06-15 16:21 ` Philippe Waroquiers
2020-06-15 20:53 ` Jonny Grant
2020-06-15 21:12 ` Pedro Alves
2020-06-15 21:28 ` Jonny Grant
2020-06-15 21:42 ` Pedro Alves
2020-06-15 11:42 ` Kamil Rytarowski
2020-06-15 15:25 ` Jonny Grant
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=5e3daadd5ee841b6f6d4ba4948849fa53ffe2107.camel@skynet.be \
--to=philippe.waroquiers@skynet.be \
--cc=gdb@sourceware.org \
--cc=jg@jguk.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).