public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: John Baldwin <jhb@FreeBSD.org>,
	gdb-patches@sourceware.org,        binutils@sourceware.org
Subject: Re: [PATCH v3 4/6] Use LWP IDs with ptrace register requests on FreeBSD.
Date: Mon, 18 Jan 2016 12:32:00 -0000	[thread overview]
Message-ID: <569CDB45.2000905@redhat.com> (raw)
In-Reply-To: <1453084047-16175-5-git-send-email-jhb@FreeBSD.org>

On 01/18/2016 02:27 AM, John Baldwin wrote:
> This allows gdb to fetch per-thread registers for multi-threaded FreeBSD
> processes.
> 
> Export get_ptrace_pid() from inf-ptrace.c and use it to determine the PID
> to pass to ptrace in pan-BSD native targets.  NetBSD and OpenBSD also accept
> LWP IDs for ptrace requests to fetch per-thread state.
> 
> gdb/ChangeLog:
> 
> 	* amd64bsd-nat.c (amd64bsd_fetch_inferior_registers): Use
> 	get_ptrace_pid.
> 	(amd64bsd_store_inferior_registers): Use get_ptrace_pid.
> 	(amd64bsd_dr_get): Use get_ptrace_pid.
> 	(amd64bsd_dr_set): Use get_ptrace_pid.
> 	* i386bsd-nat.c (i386bsd_fetch_inferior_registers): Use get_ptrace_pid.
> 	(i386bsd_store_inferior_registers): Use get_ptrace_pid.
> 	(i386bsd_dr_get): Use get_ptrace_pid.
> 	(i386bsd_dr_set): Use get_ptrace_pid.
> 	* inf-ptrace.c (get_ptrace_pid): Export.
> 	* inf-ptrace.h (get_ptrace_pid): Declare.
> 	* ppcfbsd-nat.c (ppcfbsd_fetch_inferior_registers): Use lwp id.
> 	(ppcfbsd_store_inferior_registers): Use lwp id.

LGTM.

Thanks,
Pedro Alves

  reply	other threads:[~2016-01-18 12:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18  2:28 [PATCH v3 0/6] Support kernel-backed user threads " John Baldwin
2016-01-18  2:28 ` [PATCH v3 5/6] Add support for LWP-based " John Baldwin
2016-01-18 12:37   ` Pedro Alves
2016-01-18 16:00   ` Eli Zaretskii
2016-01-18 17:06     ` John Baldwin
2016-01-18  2:28 ` [PATCH v3 4/6] Use LWP IDs with ptrace register requests " John Baldwin
2016-01-18 12:32   ` Pedro Alves [this message]
2016-01-18  2:28 ` [PATCH v3 6/6] Dump register notes for each thread when generating a FreeBSD core John Baldwin
2016-01-18 12:38   ` Pedro Alves
2016-01-18  2:28 ` [PATCH v3 2/6] Add a psuedosection for the NT_FREEBSD_THRMISC note John Baldwin
2016-01-18 12:38   ` Pedro Alves
2016-01-18 17:06     ` John Baldwin
2016-01-18  2:28 ` [PATCH v3 1/6] Add support to readelf for reading FreeBSD ELF core notes John Baldwin
2016-01-19 16:50   ` Christophe Lyon
2016-01-19 17:10     ` John Baldwin
2016-01-19 17:12       ` Pedro Alves
2016-01-18  2:28 ` [PATCH v3 3/6] Display per-thread information for threads in FreeBSD cores John Baldwin

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=569CDB45.2000905@redhat.com \
    --to=palves@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@FreeBSD.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).