qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vince Weaver <vince@csl.cornell.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] dumping processor state after each instruction executed
Date: Wed, 22 Mar 2006 09:46:00 -0500 (EST)	[thread overview]
Message-ID: <20060322094132.R10166-100000@bell.csl.cornell.edu> (raw)

Hello,

I was wondering if it is possible to insert some code into the translated
basic-block in order to dump the processor state to a file after every
single instcution?  This would be every single executed instruction,
(meaning it couldn't be just dump the state once at translation time).

I'm trying to use qemu as a frontend to the TAXI tool
  (http://www.eecs.umich.edu/~vlaovic/L150_vlaovic_s.pdf) while doing some
computer architecture work.

I've figured out how to add a helper function to the load/store routines
to get a memory trace file, but getting an instruction trace is proving to
be a bit harder.

Thanks for any help,

Vince Weaver
vince@csl.cornell.edu

                 reply	other threads:[~2006-03-22 14:46 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=20060322094132.R10166-100000@bell.csl.cornell.edu \
    --to=vince@csl.cornell.edu \
    --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).