From: John Baldwin <jhb@FreeBSD.org>
To: gdb-patches@sourceware.org, binutils@sourceware.org
Subject: [PATCH 0/2] Support for FreeBSD/mips N32
Date: Tue, 19 Sep 2017 20:48:00 -0000 [thread overview]
Message-ID: <20170919204814.93328-1-jhb@FreeBSD.org> (raw)
I finally got a chance to test FreeBSD/mipsn32 and this series addresses
the missing pieces from the earlier FreeBSD/mips changes.
The first patch to bfd/elf.c might be too hackish. Not sure if adding a
new 'bed' method for 'grok_freebsd_prstatus' is a better approach?
John Baldwin (2):
Account for padding in FreeBSD/mipsn32 NT_PRSTATUS notes.
Add a signal frame unwinder for FreeBSD/mipsn32.
bfd/ChangeLog | 6 ++++++
bfd/elf.c | 5 ++++-
gdb/ChangeLog | 7 +++++++
gdb/mips-fbsd-tdep.c | 18 ++++++++++++++++++
4 files changed, 35 insertions(+), 1 deletion(-)
--
2.13.3
next reply other threads:[~2017-09-19 20:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 20:48 John Baldwin [this message]
2017-09-19 20:48 ` [PATCH 1/2] Account for padding in FreeBSD/mipsn32 NT_PRSTATUS notes John Baldwin
2017-09-19 20:48 ` [PATCH 2/2] Add a signal frame unwinder for FreeBSD/mipsn32 John Baldwin
2017-10-11 11:16 ` Pedro Alves
2017-09-20 2:01 ` [PATCH 0/2] Support for FreeBSD/mips N32 Alan Modra
2017-09-20 4:25 ` John Baldwin
2017-09-26 21:09 ` 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=20170919204814.93328-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