From: Jonny Grant <jg@jguk.org>
To: gdb@sourceware.org
Subject: gdb show thread names
Date: Sat, 13 Jun 2020 01:16:43 +0100 [thread overview]
Message-ID: <030e3603-12ab-d3cb-afe7-2628acbc18e3@jguk.org> (raw)
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 reply other threads:[~2020-06-13 0:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-13 0:16 Jonny Grant [this message]
2020-06-13 12:47 ` Philippe Waroquiers
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=030e3603-12ab-d3cb-afe7-2628acbc18e3@jguk.org \
--to=jg@jguk.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).