From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v3 0/7] Thread handle to thread info mapping
Date: Wed, 19 Jul 2017 00:42:00 -0000 [thread overview]
Message-ID: <20170718174156.5da204b0@pinnacle.lan> (raw)
This patch set introduces support 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 (e.g. pthread_t)
within an implementation of a thread library built atop pthreads.
The mechanism is general enough however to support other thread
handle representations as well.
Simon reviewed the v2 version of these patches and found a number
of problems. I believe I have addressed all of these in this new
patch set.
Pedro noticed a fundamental problem with v2 patch series - the
mapping operation did not take into account the inferior! After a
fork, the parent and the child will have the same sets of thread
handles at the same addresses. These v3 patches also address this
problem.
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. It has been adjusted to address Eli's
concerns in an earlier patch series. Simon also proposed some changes
which I've incorporated.
Part 4 adds a test case. I've incorporated Simon's suggestions from
his review of the v2 patchset.
Part 5 is a bug fix for a problem discovered while working on part 6.
Part 6 adds support for remote targets.
Part 7 is a documentation patch for the remote protocol changes that
were implemented in part 6.
next reply other threads:[~2017-07-19 0:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 0:42 Kevin Buettner [this message]
2017-07-19 0:54 ` [PATCH v3 1/7] Add target method for converting thread handle to thread_info struct pointer Kevin Buettner
2017-07-23 20:39 ` Simon Marchi
2017-07-19 0:54 ` [PATCH v3 2/7] Add `thread_from_thread_handle' method to (Python) gdb.Inferior Kevin Buettner
2017-07-23 20:53 ` Simon Marchi
2017-07-19 0:55 ` [PATCH v3 5/7] Add thread_db_notice_clone to gdbserver Kevin Buettner
2017-07-23 21:27 ` Simon Marchi
2017-07-19 0:55 ` [PATCH v3 3/7] Documentation for Inferior.thread_from_thread_handle Kevin Buettner
2017-07-19 2:33 ` Eli Zaretskii
2017-07-19 0:55 ` [PATCH v3 4/7] Test case " Kevin Buettner
2017-07-23 21:17 ` Simon Marchi
2017-07-19 0:56 ` [PATCH v3 6/7] Add thread_handle_to_thread_info support for remote targets Kevin Buettner
2017-07-23 21:47 ` Simon Marchi
2017-07-19 0:56 ` [PATCH v3 7/7] Documentation for qXfer:threads:read handle attribute Kevin Buettner
2017-07-19 2:34 ` 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=20170718174156.5da204b0@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).