From: Dhruv Agarwal <dhruv.agarwal_ug19@ashoka.edu.in>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] QEMU 3.1 - Getting Instruction Traces
Date: Sat, 12 Jan 2019 17:30:31 +0530 [thread overview]
Message-ID: <CADKdUyQad_gm_z0GJC+XNV4EOw+U8Fb8uBHc-8=9pzTmBf+cpQ@mail.gmail.com> (raw)
Dear Developers,
I am an undergraduate student trying to generate *a trace of all
instructions executed by the QEMU ARM emulator when it runs a given binary*.
I have been using the* following command* (from an out-of-tree build from
source code):
arm-linux-user/qemu-arm -d in_asm ~/Desktop/hello
(hello is the name of my binary cross-compiled for ARM
using gcc-arm-none-eabi on an x86 host machine).
By doing this, I do get a list of translation blocks that are executed by
the emulator, however I was told by a colleague that this trace/log is
incomplete because of the following reason: the translation blocks already
in the translation cache are not translated again, and hence are not logged
to the screen by QEMU.
Hence, I am now stuck and r*equire a way to generate a complete instruction
trace of all instructions that are executed by the ARM emulator for a given
binary*. Has anyone done the same earlier and can guide me on how to get
this trace?
Thank you and best regards,
Dhruv
reply other threads:[~2019-01-12 12:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CADKdUyQad_gm_z0GJC+XNV4EOw+U8Fb8uBHc-8=9pzTmBf+cpQ@mail.gmail.com' \
--to=dhruv.agarwal_ug19@ashoka.edu.in \
--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).