qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mulyadi Santosa <mulyadi.santosa@gmail.com>
To: Remco Vermeulen <rvn270@few.vu.nl>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Logging instructions in single step mode
Date: Mon, 4 May 2009 11:26:33 +0700	[thread overview]
Message-ID: <f284c33d0905032126g5a84b4ej1218e24cd22ec7bc@mail.gmail.com> (raw)
In-Reply-To: <75019235-14F9-4791-8E7F-85581D46B106@few.vu.nl>

Hi Remco...

It's been awhile since I did brief pre-TCG qemu code analysis, but
here's my thought...

On Sat, May 2, 2009 at 2:39 AM, Remco Vermeulen <rvn270@few.vu.nl> wrote:
> Hello everyone,
>
> I'm currently working on modification where I would like to log the
> instructions executed when the cpu is in single step mode. Since the
> current_tb is null, probably because the cpu is in single step mode I can't
> use that tb.
> I could access the memory pointed to by the instruction pointer, but I don't
> know the length of the instruction.

How about checking disas_insn() in target-i386/translate.c ? I think
no matter what the current mode is (non single step or not), in some
ways this function should be called.

About checking the length of the instruction, i can not give too many
thoughts here. However, in the same function, probably you can mimic
how Qemu does code analysis.

regards,

Mulyadi.

      reply	other threads:[~2009-05-04  4:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-01 19:39 [Qemu-devel] Logging instructions in single step mode Remco Vermeulen
2009-05-04  4:26 ` Mulyadi Santosa [this message]

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=f284c33d0905032126g5a84b4ej1218e24cd22ec7bc@mail.gmail.com \
    --to=mulyadi.santosa@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rvn270@few.vu.nl \
    /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).