From: _Vince_ <vincentpoy@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re[Qemu-devel] vision [5640] breaks kqemu on Windows Host
Date: Thu, 4 Dec 2008 22:48:48 -0800 (PST) [thread overview]
Message-ID: <20848614.post@talk.nabble.com> (raw)
Test host: Windows XP 32 bits
Test system: KNOPPIX_V5.1.1CD-2007-01-04-EN.iso &
ubuntu-8.04.1-desktop-i386.iso
qemu: SVN compiled with mingw GCC 345
Revision [5639] runs OK with kqemu
Revisions [5640+] seg fault with kqemu but runs ok without kqemu
Until revision [5693], runs OK if using migration-tcp.c [5639]
After revision [5693], migration-tcp.c refactoring carries over the issue
=> Revision [5640]
Program received signal SIGSEGV, Segmentation fault.
kqemu_cpu_exec (env=0xdb5a090) at K:/Dev/EclipseProjects/QEmu/kqemu.c:478
478 asm volatile ("fxrstor %0" : "=m" (*fp));
(gdb) info stack
#0 kqemu_cpu_exec (env=0xdb5a090) at
K:/Dev/EclipseProjects/QEmu/kqemu.c:478
#1 0x004a19d3 in cpu_x86_exec (env1=0x0)
at K:/Dev/EclipseProjects/QEmu/cpu-exec.c:353
#2 0x00408628 in main (argc=0, argv=0x1783)
at K:/Dev/EclipseProjects/QEmu/vl.c:4614
(gdb)
=> Revision [5880]
Program received signal SIGSEGV, Segmentation fault.
kqemu_cpu_exec (env=0xdbda090) at K:/Dev/EclipseProjects/QEmu/kqemu.c:478
478 asm volatile ("fxrstor %0" : "=m" (*fp));
(gdb) info stack
#0 kqemu_cpu_exec (env=0xdbda090) at
K:/Dev/EclipseProjects/QEmu/kqemu.c:478
#1 0x004afba2 in cpu_x86_exec (env1=0x0)
at K:/Dev/EclipseProjects/QEmu/cpu-exec.c:314
#2 0x00406952 in main (argc=0, argv=0x1783)
at K:/Dev/EclipseProjects/QEmu/vl.c:3704
(gdb)
--
View this message in context: http://www.nabble.com/Revision--5640--breaks-kqemu-on-Windows-Host-tp20848614p20848614.html
Sent from the QEMU - Dev mailing list archive at Nabble.com.
reply other threads:[~2008-12-05 6:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20848614.post@talk.nabble.com \
--to=vincentpoy@gmail.com \
--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).