From: "Alexander E. Patrakov" <patrakov@ums.usu.ru>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Something is probably wrong with "int 3"
Date: Tue, 04 Jan 2005 18:09:32 +0500 [thread overview]
Message-ID: <cre4fv$at9$1@sea.gmane.org> (raw)
Hello, I suspect the following to be a bug in qemu.
Earlier in the Firefox-related thread, I attached the crash report from
DrWatson. It contained the following lines at the end:
function: DbgBreakPoint
77fa144b cc int 3
FAULT-> 77fa144c c3 ret
However, examples of similar faults from Microsoft Knowledge Base,
http://support.microsoft.com/kb/252837/EN-US/
http://support.microsoft.com/kb/194594/EN-US/
http://support.microsoft.com/kb/189474/EN-US/
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?
--
Alexander E. Patrakov
next reply other threads:[~2005-01-04 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 13:09 Alexander E. Patrakov [this message]
2005-01-04 14:35 ` [Qemu-devel] Something is probably wrong with "int 3" 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
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='cre4fv$at9$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).