From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/4] Thread handle to (GDB internal) thread object mapping
Date: Thu, 05 May 2016 21:09:00 -0000 [thread overview]
Message-ID: <20160505140938.26a084ed@pinnacle.lan> (raw)
This patch set introduces an interface/mechanism for mapping thread
handles to the thread_info structs which GDB uses to keep track of
threads in the inferiors which it's debugging. I need this in order
to find the GDB thread which corresponds to a saved thread handle (of
type pthread_t) within an implementation of a thread library built
atop pthreads.
Part 1 introduces a target method which maps a thread handle to
the corresponding internal GDB thread object, i.e. something of type
`struct thread_info *'. An implementation of this new method is
provided for the Linux thread target. Additional work will be
required, over time, for other thread targets.
Part 2 adds a python interface for the mechanism introduced in part 1.
Part 3 is a documentation patch.
Part 4 adds a test case.
next reply other threads:[~2016-05-05 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 21:09 Kevin Buettner [this message]
2016-05-05 21:12 ` [PATCH 1/4] Add target method for converting thread handle to thread_info struct pointer Kevin Buettner
2016-05-05 21:14 ` [PATCH 2/4] Add `thread_from_thread_handle' function to (Python) gdb module Kevin Buettner
2016-05-05 21:17 ` [PATCH 3/4] Documentation for gdb.thread_from_thread_handle Kevin Buettner
2016-05-06 6:31 ` Eli Zaretskii
2016-05-06 6:32 ` Eli Zaretskii
2016-05-05 21:19 ` [PATCH 4/4] Test case " Kevin Buettner
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=20160505140938.26a084ed@pinnacle.lan \
--to=kevinb@redhat.com \
--cc=gdb-patches@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