From: Richard Henderson <rth@twiddle.net>
To: Nathan DeBardeleben <ndebard@lanl.gov>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Looking for the correct way to pull register values out of QEMU
Date: Wed, 25 May 2011 11:01:49 -0700 [thread overview]
Message-ID: <4DDD440D.9050603@twiddle.net> (raw)
In-Reply-To: <4DDD3160.70603@lanl.gov>
On 05/25/2011 09:42 AM, Nathan DeBardeleben wrote:
> 1: Stop QEMU (maybe not necessary?)
> 2: Drag down the set of registers
> 3: Release QEMU (contingent on #1)
> 4: Repeat over some periodic sampling rate.
> 5: Produce a "gprof-like" graph of where the PC was during the time observed.
The gdb remote protocol is fairly simple. It would be pretty easy to start
QEMU with the -gdb tcp::port option, and write a script to grab the data you
want as well as format it as desired.
It may be even easier to write the script in python and run it within gdb itself.
r~
prev parent reply other threads:[~2011-05-25 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 16:42 [Qemu-devel] Looking for the correct way to pull register values out of QEMU Nathan DeBardeleben
2011-05-25 17:50 ` Mulyadi Santosa
2011-05-25 18:01 ` Richard Henderson [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=4DDD440D.9050603@twiddle.net \
--to=rth@twiddle.net \
--cc=ndebard@lanl.gov \
--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).