From: Ben Pfaff <blp@cs.stanford.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: valgrind functionality in qemu?
Date: Mon, 22 Nov 2004 10:14:49 -0800 [thread overview]
Message-ID: <87oehpn42u.fsf@benpfaff.org> (raw)
In-Reply-To: Pine.LNX.4.58.0411221255210.5151@wgmdd8.biozentrum.uni-wuerzburg.de
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> It would also be difficult to find the reference to the source code,
> because there is no support for working with the debug information in the
> code in QEmu that I know of. If you want to debug the Linux kernel, you
> need to hack the "-kernel" loading code for that.
It's not *that* hard, it just takes writing some code. We did
this in a simulation paper: "Understanding Data Lifetime via
Whole System Simulation" available at
<URL:http://www.stanford.edu/~blp/papers>, although our
implementation used Bochs instead of qemu because qemu wasn't
quite ready at the time.
--
Ben Pfaff
email: blp@cs.stanford.edu
web: http://benpfaff.org
next prev parent reply other threads:[~2004-11-22 18:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 21:34 [Qemu-devel] Downloaded files are corrupt Aaron McDonald
2004-11-18 21:45 ` Magnus Damm
2004-11-18 22:28 ` [Qemu-devel] " Ronald
2004-11-18 23:09 ` Ronald
2004-11-21 3:20 ` [Qemu-devel] " Julian Seward
2004-11-21 3:32 ` [Qemu-devel] valgrind functionality in qemu? Marc E. Fiuczynski
2004-11-22 12:05 ` Johannes Schindelin
2004-11-22 16:30 ` Sylvain Petreolle
2004-11-22 18:14 ` Ben Pfaff [this message]
2004-11-22 18:50 ` [Qemu-devel] " Johannes Schindelin
2004-11-22 19:17 ` Ben Pfaff
2004-11-21 16:46 ` [Qemu-devel] Downloaded files are corrupt Martin Jansa
2004-11-21 18:30 ` Julian Seward
2004-11-21 18:41 ` [Qemu-devel] " Ronald
2004-11-21 19:59 ` [Qemu-devel] " Fabrice Bellard
2004-11-21 20:32 ` Martin Jansa
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=87oehpn42u.fsf@benpfaff.org \
--to=blp@cs.stanford.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.