From: John Baldwin <jhb@freebsd.org>
To: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: [PATCH 0/6] Support kernel-backed user threads on FreeBSD
Date: Mon, 11 Jan 2016 18:53:00 -0000 [thread overview]
Message-ID: <10958096.fTGshuKdL7@ralph.baldwin.cx> (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.
John Baldwin (6):
Add support to readelf for reading FreeBSD ELF core notes.
Add a psuedosection for the NT_FREEBSD_THRMISC note.
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 | 68 ++++++++
gdb/amd64bsd-nat.c | 35 ++--
gdb/config.in | 3 +
gdb/configure | 16 ++
gdb/configure.ac | 7 +
gdb/fbsd-nat.c | 452 +++++++++++++++++++++++++++++++++++++++++++++++---
gdb/fbsd-tdep.c | 185 ++++++++++++++++++---
gdb/i386bsd-nat.c | 41 +++--
gdb/ppcfbsd-nat.c | 23 ++-
include/elf/ChangeLog | 27 +++
include/elf/common.h | 14 ++
15 files changed, 842 insertions(+), 80 deletions(-)
create mode 100644 include/elf/ChangeLog
--
2.7.0
next reply other threads:[~2016-01-11 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 18:53 John Baldwin [this message]
2016-01-12 18:55 ` John Baldwin
2016-01-12 19:06 ` Mark Kettenis
2016-01-12 19:07 ` Paul_Koning
2016-01-12 19:24 ` Pedro Alves
2016-01-12 21:08 ` 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=10958096.fTGshuKdL7@ralph.baldwin.cx \
--to=jhb@freebsd.org \
--cc=binutils@sourceware.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