From: Simon Marchi <simon.marchi@polymtl.ca>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v4 0/7] Thread handle to thread info mapping
Date: Mon, 18 Sep 2017 20:17:00 -0000 [thread overview]
Message-ID: <7126931916df05d6d7aa73c346a1a223@polymtl.ca> (raw)
In-Reply-To: <20170816092542.6d2deb00@pinnacle.lan>
On 2017-08-16 18:25, Kevin Buettner wrote:
> 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 non-documentation parts of the v3 version of this
> patch set. I think I have addressed all of his concerns from that
> review.
>
> Eli approved the two documentation patches. There have been no
> changes from v3 to v4, but I'm including them here for completeness.
>
> 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.
>
> Part 2 adds a python interface for the mechanism introduced in part 1.
>
> Part 3 is a documentation patch. As noted above, Eli has already
> approved this patch which is unchanged from the v3 patch set.
>
> Part 4 adds a test case. I've incorporated all of Simon's suggestions
> from his review of the v3 patch. I've also added three new tests
> which check the behavior of thread_from_thread_handle when passing
> a bad thread handle. After making this change, I found a problem
> in part 6.
>
> Part 5 is a bug fix for a problem discovered while working on part 6.
>
> Part 6 adds support for remote targets. In addition to making several
> v3 changes requested by Simon, I adjusted
> remote_thread_handle_to_thread_info
> so that would throw an exception (via a call to error()) when the
> handle
> sizes are mismatched.
>
> Part 7 is a documentation patch for the remote protocol changes that
> were implemented in part 6. This patch is unchanged from the v3
> version
> and has already been approved by Eli.
>
> Kevin
My previous comments were mostly nits. I took a quick look, and it
LGTM.
Thanks!
Simon
next prev parent reply other threads:[~2017-09-18 20:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 16:25 Kevin Buettner
2017-08-16 17:35 ` [PATCH v4 1/7] Add target method for converting thread handle to thread_info struct pointer Kevin Buettner
2017-08-16 17:37 ` [PATCH v4 2/7] Add `thread_from_thread_handle' method to (Python) gdb.Inferior Kevin Buettner
2017-08-16 17:38 ` [PATCH v4 3/7] Documentation for Inferior.thread_from_thread_handle Kevin Buettner
2017-08-16 17:40 ` [PATCH v4 4/7] Test case " Kevin Buettner
2017-08-16 17:41 ` [PATCH v4 5/7] Add thread_db_notice_clone to gdbserver Kevin Buettner
2017-09-29 12:24 ` Pedro Alves
2017-08-16 17:43 ` [PATCH v4 6/7] Add thread_handle_to_thread_info support for remote targets Kevin Buettner
2017-08-16 17:44 ` [PATCH v4 7/7] Documentation for qXfer:threads:read handle attribute Kevin Buettner
2017-09-13 0:00 ` [PATCH v4 0/7] Thread handle to thread info mapping Kevin Buettner
2017-09-18 20:17 ` Simon Marchi [this message]
2017-09-21 18:56 ` Kevin Buettner
2017-09-21 18:57 ` 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=7126931916df05d6d7aa73c346a1a223@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=kevinb@redhat.com \
/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