From: "Shashidhar Mysore" <shashimc@gmail.com>
To: ananaza@iki.fi, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: PC traces from QEMU
Date: Thu, 29 Mar 2007 18:25:06 -0700 [thread overview]
Message-ID: <12835c8f0703291825w6caf4e74n99c7e5f9f691cbf2@mail.gmail.com> (raw)
In-Reply-To: <87ejn80xi8.fsf@brigitte.dna.fi>
[-- Attachment #1: Type: text/plain, Size: 2154 bytes --]
Hi Antti,
Thanks for the reply. Honestly, I am new to QEMU, hence I just tried
following the steps you had mentioned to extract PCs without actually
knowing what each of those mean.
As you had said,
- I defined DEBUG_EXEC in cpu-exec.c
- I disabled USE_DIRECT_JUMP in exec-all.h
- I disabled USE_CODE_COPY in target-i386/cpu.h
- I hardcoded force_dc->jmp_opt to equal zero in target-i386/translate.c
(force_dc->jmp_opt = 0;)
However, when I try to make the qemu-0.9.0 that I have, I get the following
error -
##########################################################
$ make
....
/qemu-0.9.0-trial/target-i386/translate.c
/qemu-0.9.0-trial/target-i386/translate.c: In function `gen_goto _tb':
/qemu-0.9.0-trial/target-i386/translate.c:1766: error: too many arguments to
function `gen_op_goto_tb0'
/qemu-0.9.0-trial/target-i386/translate.c:1768: error: too many arguments to
function `gen_op_goto_tb1'
make[1]: *** [translate.o] Error 1
make[1]: Leaving directory `/qemu-0.9.0-trial/i386-linux-user'
make: *** [subdir-i386-linux-user] Error 2
######################################################
Do you know if I'm doing something wrong here? Also, since qemu-0.7 doesn't
seem to be available for download from the qemu webpage, I couldn't try the
same with qemu-0.7. I appreciate your help on this.
Thanks,
-Shashi.
On 3/29/07, Antti P Miettinen <ananaza@iki.fi> 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:
> - define DEBUG_EXEC in cpu-exec.c
> - disable USE_DIRECT_JUMP in exec-all.h
> - disable USE_CODE_COPY in target-i386/cpu.h
> - force dc->jmp_opt to zero in target-i386/translate.c
> Would be nice if enabling PC traces were possible with e.g. command
> line (maybe requiring config time enable would be good too :-)
>
> --
> http://www.iki.fi/~ananaza/
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 2680 bytes --]
prev parent reply other threads:[~2007-03-30 1:27 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
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 [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=12835c8f0703291825w6caf4e74n99c7e5f9f691cbf2@mail.gmail.com \
--to=shashimc@gmail.com \
--cc=ananaza@iki.fi \
--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).