From: John Baldwin <jhb@FreeBSD.org>
To: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: [PATCH 0/6] Add ELF auxiliary vector handling for FreeBSD
Date: Thu, 16 Jun 2016 06:02:00 -0000 [thread overview]
Message-ID: <20160616060202.63470-1-jhb@FreeBSD.org> (raw)
This patch series fixes 'info auxv' to work on live binaries and cores
for FreeBSD. I believe most of these patches are straightforward.
I broke out parsing of FreeBSD-specific ELF core notes to avoid a
collision with duplicate NT_* values (NT_FREEBSD_PROCSTAT_AUXV conflicts
with NT_LWPSTATUS). The biggest change is adding a new gdbarch method
to handle formatting individual auxv vectors. FreeBSD uses AT_* constants
that overlap with existing AT_* constants but with different meanings.
One result of making the interpretation of AT_* constants a gdbarch
method is that 'info auxv' shows the correct output (Linux values)
when gdb inspects a Linux binary executing on FreeBSD via FreeBSD's
Linux ABI support.
John Baldwin (6):
Add constants for FreeBSD-specific auxiliary vector entry types.
Add elfcore_grok_freebsd_note to parse FreeBSD ELF core notes.
Fetch the ELF auxiliary vector from live processes on FreeBSD.
Create a psuedo section for the ELF AUXV core dump note on FreeBSD.
Add a new gdbarch method to print a single AUXV entry.
Add a gdbarch 'print_auxv' method for FreeBSD ABIs.
bfd/ChangeLog | 15 ++++
bfd/elf.c | 152 +++++++++++++++++++++++++++++++++++++---
gdb/ChangeLog | 23 +++++++
gdb/auxv.c | 191 ++++++++++++++++++++++++++++-----------------------
gdb/auxv.h | 8 +++
gdb/fbsd-nat.c | 74 ++++++++++++++++++++
gdb/fbsd-tdep.c | 33 +++++++++
gdb/gdbarch.c | 32 +++++++++
gdb/gdbarch.h | 11 +++
gdb/gdbarch.sh | 6 ++
include/ChangeLog | 7 ++
include/elf/common.h | 10 +++
12 files changed, 467 insertions(+), 95 deletions(-)
--
2.8.4
next reply other threads:[~2016-06-16 6:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 6:02 John Baldwin [this message]
2016-06-16 6:02 ` [PATCH 2/6] Add elfcore_grok_freebsd_note to parse FreeBSD ELF core notes John Baldwin
2016-06-17 8:28 ` Nick Clifton
2016-06-16 6:02 ` [PATCH 1/6] Add constants for FreeBSD-specific auxiliary vector entry types John Baldwin
2016-06-17 8:27 ` Nick Clifton
2016-06-16 6:02 ` [PATCH 6/6] Add a gdbarch 'print_auxv' method for FreeBSD ABIs John Baldwin
2016-06-20 23:43 ` Pedro Alves
2016-06-16 6:02 ` [PATCH 3/6] Fetch the ELF auxiliary vector from live processes on FreeBSD John Baldwin
2016-06-20 23:01 ` Pedro Alves
2016-06-16 6:11 ` [PATCH 5/6] Add a new gdbarch method to print a single AUXV entry John Baldwin
2016-06-20 23:40 ` Pedro Alves
2016-06-23 20:19 ` John Baldwin
2016-06-16 6:11 ` [PATCH 4/6] Create a psuedo section for the ELF AUXV core dump note on FreeBSD John Baldwin
2016-06-17 8:28 ` Nick Clifton
2016-06-20 23:45 ` Pedro Alves
2016-06-20 17:10 ` [PATCH 0/6] Add ELF auxiliary vector handling for FreeBSD 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=20160616060202.63470-1-jhb@FreeBSD.org \
--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