after some debugging I confirmed that this is caused by a mingw gcc
4.6.1-2 optiomization bug, gcc generated optimized code that used ebp to
store some results , while later ebp is used in setjmp and longjmp, so
a beiju occurred. mingw gcc 4.5.2works well. the bug should be closed.
--
You recei
maybe it's caused by mingw/gcc? the same binary runs well on win7-x64,
but not on win2003-32 bit I'll do more test, if I've time, i'd debug it
and try to find the reason
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.lau
Public bug reported:
qemu-1.0-rc2/cpu-exec.c:37 longjmp(env->jmp_env, 1); it seems that env->jmp_env
destroyed, (gdb) p env->jmp_env
$3 = {0, 0, 0, 36249608, 41418280, 5303318, 41418664, 0, 0, 0, 0, 0, 0, 0, 0, 0}
** Affects: qemu
Importance: Undecided
Status: New
--
You received
it's compiled on windows 2003 and using mingw gcc version 4.6.1
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/891002
Title:
windows mingw compiled qemu-system-x86_64 crash on startup
Status in QEM
