From: Richard Henderson <rth@twiddle.net>
To: qemu-devel@nongnu.org
Cc: jcmvbkbc@gmail.com, gxt@mprc.pku.edu.cn, proljc@gmail.com,
claudio.fontana@gmail.com, peter.maydell@linaro.org
Subject: [Qemu-devel] [PATCH 0/2] Disassembly with external objdump
Date: Fri, 9 Aug 2013 09:19:16 -1000 [thread overview]
Message-ID: <1376075958-21932-1-git-send-email-rth@twiddle.net> (raw)
We have one host platform (aarch64), and three target platforms
(openrisc, unicore32, xtensa) with no built-in disassembly support,
thanks largely to gplv3 silliness.
Here's a first-cut at handling these cases with an external tool.
The qemu-produced dump file contains just a hex dump of bytes, and
a perl script is provided to pass those bytes through objdump.
I've lightly tested this with aarch64 host running on Foundation.
Feedback appreciated.
r~
Richard Henderson (2):
disas: Implement fallback to dump object code as hex
disas: Add disas-objdump.pl
disas.c | 46 +++++++++++++++++++------
scripts/disas-objdump.pl | 87 ++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 123 insertions(+), 10 deletions(-)
create mode 100755 scripts/disas-objdump.pl
--
1.8.3.1
next reply other threads:[~2013-08-09 19:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 19:19 Richard Henderson [this message]
2013-08-09 19:19 ` [Qemu-devel] [PATCH 1/2] disas: Implement fallback to dump object code as hex Richard Henderson
2013-08-09 19:19 ` [Qemu-devel] [PATCH 2/2] disas: Add disas-objdump.pl Richard Henderson
2013-08-10 4:08 ` Max Filippov
2013-08-10 10:39 ` Richard Henderson
2013-08-10 1:54 ` [Qemu-devel] [PATCH 0/2] Disassembly with external objdump Jia Liu
2013-08-10 9:16 ` Peter Maydell
2013-08-10 10:22 ` Claudio Fontana
2013-08-10 15:45 ` Peter Maydell
2013-08-10 16:42 ` Richard Henderson
2013-08-10 16:53 ` Max Filippov
2013-08-10 19:47 ` Richard Henderson
2013-09-03 13:18 ` Claudio Fontana
2013-08-11 8:59 ` Blue Swirl
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=1376075958-21932-1-git-send-email-rth@twiddle.net \
--to=rth@twiddle.net \
--cc=claudio.fontana@gmail.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=jcmvbkbc@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=proljc@gmail.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).