From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Clemens Kolbitsch <clemens.kol@gmx.at>
Subject: Re: [Qemu-devel] Debugging guest OS / tracing instruction pointer
Date: Thu, 14 Jun 2007 16:03:52 +0100 [thread overview]
Message-ID: <200706141603.52939.paul@codesourcery.com> (raw)
In-Reply-To: <467152A6.9060805@gmx.at>
On Thursday 14 June 2007, Clemens Kolbitsch wrote:
> hi!
> i'm looking for a way to monitor the eip register. is there a simple way
> to do this? i know that that produces tons of data...
>
> even better would be to know where i could intercept the main-loop
> (exec_cpu ??) to check for a certain eip value...
qemu already has mechanisms for supporting debugger breakpoints. Sounds like
you want something very similar.
Paul
next prev parent reply other threads:[~2007-06-14 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070606095708.28535gmx1@mx017.gmx.net>
2007-06-14 14:37 ` [Qemu-devel] Debugging guest OS / tracing instruction pointer Clemens Kolbitsch
2007-06-14 15:03 ` Paul Brook [this message]
2007-06-14 15:21 ` Clemens Kolbitsch
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=200706141603.52939.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=clemens.kol@gmx.at \
--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).