Re: [Qemu-devel] Re: Something is probably wrong with "int 3"

[Johannes Schindelin]

Hi,

On Tue, 4 Jan 2005, Alexander E. Patrakov wrote:

> Andr? Braga wrote:
>
> > On Tue, 04 Jan 2005 18:09:32 +0500, Alexander E. Patrakov
> > <address@hidden> wrote:
> >> clearly state that the fault is at the "int 3" instruction, not at "ret".
> >> Can anyone explain this difference? Is this a bug in qemu?

That is quite normal. As int 3 is already executed when the pop up is
triggered, the program counter in that frame points to the next insn.

> Look at the crash dump - the DbgBreakPoint() is called from
> kernel32!SetThreadExecutionState, i.e. from deep inside the Windows kernel.

If DbgBreakPoint() is called, this normally means that a DebugAssertion
was called, which is not fulfilled.

Can you inspect what's going on in SetThreadExecutionState before the
INT 3 (I mean disassemble it and tell us what Windows is trying to do)?
This should help understand the problem.

Ciao,
Dscho