From: maestro <maestro82@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Tracing guest memory accesses
Date: Mon, 18 Dec 2006 20:49:25 +0100 [thread overview]
Message-ID: <1166471365.4186.17.camel@localhost.localdomain> (raw)
In-Reply-To: <891be9410612180056j48be1981v2a62a4668f9da050@mail.gmail.com>
Am Montag, den 18.12.2006, 00:56 -0800 schrieb Diwaker Gupta:
> > as far as i remember i had to put the same code into softmmu_header.h to
> > get "correct" results.
> > i found it easiest to do this in the ld/st macros in these files (~6
> > places in code)
>
> This probably sounds stupid but whats the best way to get debug
> output? Due to the code generation magic qemu does, simply adding
> printfs doesn't seem to work well. In particular, all my attempts to
> add printfs to softmmu_header.h have resulted in broken builds. Are
> there any global macros I should be using?
>
hello Diwaker!
you can always call a function that is defined extern that uses fprintf
et. al. i doubt it's the prettiest way but at least it works.
cheers
m.
prev parent reply other threads:[~2006-12-18 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-17 3:42 [Qemu-devel] Tracing guest memory accesses Diwaker Gupta
2006-12-17 3:53 ` Daniel Jacobowitz
2006-12-17 7:19 ` Diwaker Gupta
2006-12-17 11:52 ` maestro
2006-12-18 8:56 ` Diwaker Gupta
2006-12-18 19:49 ` maestro [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=1166471365.4186.17.camel@localhost.localdomain \
--to=maestro82@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).