From: John Baldwin <jhb@FreeBSD.org>
To: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: [PATCH v2 0/4] Initial support for FreeBSD/arm in GDB
Date: Fri, 22 Sep 2017 22:58:00 -0000 [thread overview]
Message-ID: <20170922225713.26609-1-jhb@FreeBSD.org> (raw)
This series adds initial support for FreeBSD/arm to GDB. It does not
include support for hardware watchpoints or breakpoints.
Relative to V1, patch 3 contains some additional changes to account
for HWCAP_* renumbering in FreeBSD to align with Linux as well as
handling HWCAP_NEON.
John Baldwin (4):
Handle FreeBSD-specific AT_EHDRFLAGS and AT_HWCAP auxiliary vector
types.
Handle the NT_ARM_VFP core dump note on FreeBSD.
Add FreeBSD/arm architecture.
Add native target for FreeBSD/arm.
bfd/ChangeLog | 4 +
bfd/elf.c | 3 +
gdb/ChangeLog | 22 +++++
gdb/Makefile.in | 3 +
gdb/NEWS | 2 +
gdb/arm-fbsd-nat.c | 151 ++++++++++++++++++++++++++++++
gdb/arm-fbsd-tdep.c | 260 +++++++++++++++++++++++++++++++++++++++++++++++++++
gdb/arm-fbsd-tdep.h | 40 ++++++++
gdb/configure.host | 1 +
gdb/configure.nat | 5 +
gdb/configure.tgt | 5 +
gdb/fbsd-tdep.c | 2 +
include/ChangeLog | 4 +
include/elf/common.h | 2 +
14 files changed, 504 insertions(+)
create mode 100644 gdb/arm-fbsd-nat.c
create mode 100644 gdb/arm-fbsd-tdep.c
create mode 100644 gdb/arm-fbsd-tdep.h
--
2.13.3
next reply other threads:[~2017-09-22 22:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 22:58 John Baldwin [this message]
2017-09-22 22:58 ` [PATCH v2 1/4] Handle FreeBSD-specific AT_EHDRFLAGS and AT_HWCAP auxiliary vector types John Baldwin
2017-09-22 22:58 ` [PATCH v2 2/4] Handle the NT_ARM_VFP core dump note on FreeBSD John Baldwin
2017-09-22 22:58 ` [PATCH v2 3/4] Add FreeBSD/arm architecture John Baldwin
2017-09-22 23:07 ` [PATCH v2 4/4] Add native target for FreeBSD/arm John Baldwin
2017-09-24 23:49 ` [PATCH v2 0/4] Initial support for FreeBSD/arm in GDB Alan Modra
2017-09-29 17:46 ` John Baldwin
2017-10-11 11:14 ` Pedro Alves
2017-10-11 17:07 ` 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=20170922225713.26609-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).