From: Robert Riebisch <rr@bttr-software.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] QEMU 0.10.0 crash on Win32
Date: Thu, 05 Mar 2009 23:16:43 +0100 [thread overview]
Message-ID: <49B04F4B.3000401@bttr-software.de> (raw)
Hi!
Firstly, thanks to all contributors for the new release! :-)
While QEMU 0.10.0 built using MinGW GCC 3.4.5 runs fine with KQEMU
enabled, a build made with GCC 4.3.0 (alpha) crashes on Win32, when
booting Avira's Rescue System ISO.
***
Program received signal SIGSEGV, Segmentation fault.
kqemu_cpu_exec (env=0x3d9e2ff8)
at C:/msys/1.0/home/Robert/qemu-0.10.0/kqemu.c:475
475 asm volatile ("fxrstor %0" : "=m" (*fp));
(gdb) warning: Lowest section in C:\WINNT\system32\mfc42loc.dll is .rsrc
at 6c1d1000
***
Host CPU: Pentium M (Banias)
Host OS: Windows 2000 Pro SP4
KQEMU version: 1.4.0pre1
Any idea?
Robert Riebisch
--
BTTR Software
http://www.bttr-software.de/
next reply other threads:[~2009-03-05 22:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 22:16 Robert Riebisch [this message]
2009-03-06 7:19 ` [Qemu-devel] QEMU 0.10.0 crash on Win32 Teemu Nätkinniemi
2009-03-06 19:58 ` Robert Riebisch
2009-03-06 20:41 ` Doug Schaefer
2009-03-06 20:58 ` Robert Riebisch
2009-03-06 21:04 ` Doug Schaefer
2009-03-06 21:32 ` Robert Riebisch
2009-03-06 21:49 ` Robert Riebisch
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=49B04F4B.3000401@bttr-software.de \
--to=rr@bttr-software.de \
--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).