This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v2 0/7] Thread handle to thread info mapping
- From: Kevin Buettner <kevinb at redhat dot com>
- To: gdb-patches at sourceware dot org
- Date: Wed, 3 May 2017 11:32:26 -0700
- Subject: Re: [PATCH v2 0/7] Thread handle to thread info mapping
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx10.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx10.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=kevinb at redhat dot com
- Dkim-filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 6B31E61D03
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 6B31E61D03
- References: <20170408224959.67164a27@pinnacle.lan>
Ping!
On Sat, 8 Apr 2017 22:49:59 -0700
Kevin Buettner <kevin@buettner.to> 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.
>
> 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 the earlier patch series.
>
> Part 4 adds a test case. I've extended this test case slightly from the
> patch in the earlier series.
>
> 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.