* [Qemu-devel] Debugging guest OS / tracing instruction pointer
[not found] <20070606095708.28535gmx1@mx017.gmx.net>
@ 2007-06-14 14:37 ` Clemens Kolbitsch
2007-06-14 15:03 ` Paul Brook
0 siblings, 1 reply; 3+ messages in thread
From: Clemens Kolbitsch @ 2007-06-14 14:37 UTC (permalink / raw)
To: qemu-devel
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...
could someone assist me doing that?
thanks!
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] Debugging guest OS / tracing instruction pointer
2007-06-14 14:37 ` [Qemu-devel] Debugging guest OS / tracing instruction pointer Clemens Kolbitsch
@ 2007-06-14 15:03 ` Paul Brook
2007-06-14 15:21 ` Clemens Kolbitsch
0 siblings, 1 reply; 3+ messages in thread
From: Paul Brook @ 2007-06-14 15:03 UTC (permalink / raw)
To: qemu-devel; +Cc: Clemens Kolbitsch
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] Debugging guest OS / tracing instruction pointer
2007-06-14 15:03 ` Paul Brook
@ 2007-06-14 15:21 ` Clemens Kolbitsch
0 siblings, 0 replies; 3+ messages in thread
From: Clemens Kolbitsch @ 2007-06-14 15:21 UTC (permalink / raw)
To: Paul Brook; +Cc: qemu-devel
Paul Brook wrote:
> 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
>
the thing is: i want to monitor the eip... or where the code will jump
NEXT. the code there is never executed (as it results in a kernel failure)
e.g. i know a buffer overflow will set the return-pointer to 0xABCD and
"ret" is executed i want the breakpoint to hit
when using casual breakpoints, i think the code there must be executed
(i.e. the jump must be successful .. what will definitely not be the
case with 0xABCD)
thanks!
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2007-06-14 15:21 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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
2007-06-14 15:21 ` Clemens Kolbitsch
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).