From: <Paul_Koning@Dell.com>
To: <gdb@sourceware.org>
Subject: Thread name in remote stub protocol
Date: Wed, 24 Jun 2015 20:02:00 -0000 [thread overview]
Message-ID: <CC0C9FC0-EAF7-4A33-B29B-660557220642@dell.com> (raw)
I’ve been looking into FreeBSD threads support, and gdbserver support. FreeBSD has the notion of thread names, and it’s easy enough to make native GDB handle that. gdbserver is another matter. I looked all over the various thread related messages, and while there are a bunch of opportunities for this to be handled, it isn’t really there.
I can see the deprecated qP packet that carries a “shortname”. That looks interesting, but while the packet parsing is there, it isn’t clear the value goes anywhere. Similarly, there is qThreadExtraInfo which allows for a free form string. And there is qXfer:threads, but that carries only an ID and a core number. And none of these seem to be cleanly tied to the main gdb thread name machinery.
What to do about this? Could qXfer:threads be extended to add a thread name field? Or should I just use the ThreadExtraInfo mechanism and ignore the fact that it conveys extra info rather than the thread name?
paul
next reply other threads:[~2015-06-24 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 20:02 Paul_Koning [this message]
2015-06-25 9:28 ` Pedro Alves
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=CC0C9FC0-EAF7-4A33-B29B-660557220642@dell.com \
--to=paul_koning@dell.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