From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Something is probably wrong with "int 3"
Date: Wed, 05 Jan 2005 15:07:38 +0500 [thread overview]
Message-ID: <crge6r$6d1$1@sea.gmane.org> (raw)
In-Reply-To: crg54l$hr4$1@sea.gmane.org
Alexander E. Patrakov wrote:
> Johannes Schindelin wrote:
>
>> 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
>>> > <patrakov@ums.usu.ru> 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.
>
> I will nevertheless check that by means of writing and executing a test
> program.
Well, I am totally confused. The test program is:
#include <windows.h>
int APIENTRY WinMain(HINSTANCE p1, HINSTANCE p2, LPSTR p3, int p4)
{
DebugBreak();
return 0;
}
As expected, this crashes, and the fault is at "int 3" in qemu. So it looks
like no bug is here. But then, why does Firefox produce a visible fault at
"ret", not at "int 3"? Maybe there's some exception handler that handles
the first exception on "int 3" and then the second, unhandled, exception is
produced on "ret"?
--
Alexander E. Patrakov
prev parent reply other threads:[~2005-01-05 10:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 13:09 [Qemu-devel] Something is probably wrong with "int 3" Alexander E. Patrakov
2005-01-04 14:35 ` André Braga
2005-01-04 14:55 ` [Qemu-devel] " Alexander E. Patrakov
2005-01-04 17:05 ` Johannes Schindelin
2005-01-05 7:32 ` Alexander E. Patrakov
2005-01-05 10:07 ` Alexander E. Patrakov [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='crge6r$6d1$1@sea.gmane.org' \
--to=patrakov@ums.usu.ru \
--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).