From: Richard Henderson <rth@twiddle.net>
To: "Boris Cámara" <vesmar@rocketmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] full dynamic instruction trace for MIPS target
Date: Mon, 05 Apr 2010 15:41:52 -0700 [thread overview]
Message-ID: <4BBA6730.8000102@twiddle.net> (raw)
In-Reply-To: <639622.90232.qm@web43140.mail.sp1.yahoo.com>
On 04/05/2010 03:09 PM, Boris Cámara wrote:
> I think the correct way to get the full instruction trace on a MIPS
> emulated processor is:
-singlestep -d exec
That gives you the address of each instruction executed.
I'm not sure what else you want than this, as you havn't said.
r~
next prev parent reply other threads:[~2010-04-05 22:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 22:09 [Qemu-devel] full dynamic instruction trace for MIPS target Boris Cámara
2010-04-05 22:41 ` Richard Henderson [this message]
2010-04-05 23:24 ` Res: " Boris Cámara
2010-04-06 1:41 ` Vince Weaver
2010-04-06 23:18 ` Res: " Boris Cámara
2010-04-07 2:33 ` Vince Weaver
2010-04-07 16:42 ` Res: " Boris Cámara
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=4BBA6730.8000102@twiddle.net \
--to=rth@twiddle.net \
--cc=qemu-devel@nongnu.org \
--cc=vesmar@rocketmail.com \
/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).