qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "andrzej zaborowski" <balrog@zabor.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: PC traces from QEMU
Date: Thu, 29 Mar 2007 23:42:35 +0200	[thread overview]
Message-ID: <fb249edb0703291442t29e7994bqdfee5ae032d2264f@mail.gmail.com> (raw)
In-Reply-To: <20070329203736.GA7024@miranda.arrow>

On 29/03/07, Stuart Brady <sdbrady@ntlworld.com> wrote:
> On Thu, Mar 29, 2007 at 08:29:03PM +0300, Antti P Miettinen wrote:
> > "Shashidhar Mysore" <shashimc@gmail.com> writes:
> > > I intend to extract program counter streams from QEMU as a program executes.
> > > Can you please point me to the hooks that I may have to insert into the QEMU
> > > source code in order to extract the PC values?
> >
> > I used to do that with qemu 0.7. I did not dig into this deep enough
> > to find the minimal changes but at least the following was enough:
> [...]
> > - force dc->jmp_opt to zero in target-i386/translate.c
>
> I don't quite see where you would do this.
>
> BTW, the approach I took was to add something like gen_op_dump_pc(s->pc)
> near the top of disas_insn (in translate.c), and have op_dump_pc (in
> op.c) pass the program counter (held in PARAM1) to a helper (in
> helper.c) that then prints it out.  I expect that's not the best
> approach, but it worked quite well for my purposes.

The approach I took was call "cpu_single_step(env, 1); vm_start();
return;" in gdb_vm_stopped in gdbstub.c. Then after I connect to qemu
with gdb the first time it single steps in a loop - probably very
inefficient but works.

Just my two cents.
Andrzej

  reply	other threads:[~2007-03-29 21:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26 20:13 [Qemu-devel] PC traces from QEMU Shashidhar Mysore
2007-03-29 17:29 ` [Qemu-devel] " Antti P Miettinen
2007-03-29 20:37   ` Stuart Brady
2007-03-29 21:42     ` andrzej zaborowski [this message]
2007-03-30  1:28     ` Shashidhar Mysore
2007-03-30 11:10       ` Stuart Brady
2007-04-02 22:32         ` Shashidhar Mysore
2007-04-02 23:17           ` Thiemo Seufer
2007-03-30  1:25   ` Shashidhar Mysore

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=fb249edb0703291442t29e7994bqdfee5ae032d2264f@mail.gmail.com \
    --to=balrog@zabor.org \
    --cc=balrogg@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).