From: John Baldwin <jhb@FreeBSD.org>
To: gdb-patches@sourceware.org
Subject: [PATCH v4 0/7] Support kernel-backed user threads on FreeBSD
Date: Mon, 18 Jan 2016 18:38:00 -0000 [thread overview]
Message-ID: <1453142254-20266-1-git-send-email-jhb@FreeBSD.org> (raw)
This set of patches adds support for examining kernel-backed user threads on
FreeBSD. There is more history in a comment in fbsd-nat.c, but this target
uses ptrace directly (instead of libthread_db) to support the current
threading library (libthr) on FreeBSD which uses a kernel thread for each
user thread. Support for thread names in both core dumps (via FreeBSD's
OS-specific NT_THRMISC core note) and live is supported as is scheduler
locking. gcore generates register notes for each thread as well.
The first two patches are to binutils to support FreeBSD-specific core
notes. The last four are to GDB.
I've dropped binutils@ since the binutils patches have already been
ok'd and they haven't changed.
Relative to the previous version, this adds a new 'core_thread_name'
gdbarch method and moves the logic to fetch thread names for cores out of
fbsd_core_pid_to_str to a new fbsd_core_thread_name function.
John Baldwin (7):
Add support to readelf for reading FreeBSD ELF core notes.
Add a psuedosection for the NT_FREEBSD_THRMISC note.
Add support for extracting thread names from cores.
Display per-thread information for threads in FreeBSD cores.
Use LWP IDs with ptrace register requests on FreeBSD.
Add support for LWP-based threads on FreeBSD.
Dump register notes for each thread when generating a FreeBSD core.
bfd/ChangeLog | 4 +
bfd/elf.c | 7 +
binutils/ChangeLog | 5 +
binutils/readelf.c | 35 +++++
gdb/ChangeLog | 82 ++++++++++
gdb/NEWS | 6 +
gdb/amd64bsd-nat.c | 24 +--
gdb/config.in | 3 +
gdb/configure | 16 ++
gdb/configure.ac | 7 +
gdb/corelow.c | 10 ++
gdb/doc/ChangeLog | 4 +
gdb/doc/gdb.texinfo | 5 +
gdb/fbsd-nat.c | 423 +++++++++++++++++++++++++++++++++++++++++++++++----
gdb/fbsd-tdep.c | 210 +++++++++++++++++++++----
gdb/gdbarch.c | 32 ++++
gdb/gdbarch.h | 9 ++
gdb/gdbarch.sh | 4 +
gdb/i386bsd-nat.c | 30 ++--
gdb/inf-ptrace.c | 2 +-
gdb/inf-ptrace.h | 5 +
gdb/ppcfbsd-nat.c | 12 +-
include/ChangeLog | 13 ++
include/elf/common.h | 14 ++
24 files changed, 870 insertions(+), 92 deletions(-)
--
2.7.0
next reply other threads:[~2016-01-18 18:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 18:38 John Baldwin [this message]
2016-01-18 18:38 ` [PATCH v4 3/7] Add support for extracting thread names from cores John Baldwin
2016-01-19 10:39 ` Pedro Alves
2016-01-18 18:38 ` [PATCH v4 2/7] Add a psuedosection for the NT_FREEBSD_THRMISC note John Baldwin
2016-01-19 10:39 ` Pedro Alves
2016-01-19 16:02 ` John Baldwin
2016-01-18 18:38 ` [PATCH v4 6/7] Add support for LWP-based threads on FreeBSD John Baldwin
2016-01-19 10:39 ` Pedro Alves
2016-01-18 18:38 ` [PATCH v4 7/7] Dump register notes for each thread when generating a FreeBSD core John Baldwin
2016-01-19 10:39 ` Pedro Alves
2016-01-18 18:38 ` [PATCH v4 1/7] Add support to readelf for reading FreeBSD ELF core notes John Baldwin
2016-01-18 18:47 ` [PATCH v4 5/7] Use LWP IDs with ptrace register requests on FreeBSD John Baldwin
2016-01-19 10:39 ` Pedro Alves
2016-01-18 18:47 ` [PATCH v4 4/7] Display per-thread information for threads in FreeBSD cores John Baldwin
2016-01-19 10:39 ` Pedro Alves
2016-01-19 16:02 ` 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=1453142254-20266-1-git-send-email-jhb@FreeBSD.org \
--to=jhb@freebsd.org \
--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).