Hi Stefan, I am using released 1.5.0 version from http://wiki.qemu.org/Download. I think it should be same as commit ID "295d81c62414a63c625fa2e78175573d4b3f5ba4"
I have observed some interesting behavior. This problem does not come if I use MinGW with GCC version 4.7.2. I was originally using 4.6.2. I spent some time looking at what can cause this problem and found out an interesting thing. If I change optimization flag from O2 to O1 while building coroutine-win32 then it works fine even with 4.6.2. For this I first built QEMU binary with default O2 flag, remove coroutine-win32.o, changed CFLAG in makefile to O1 and rerun make. Generated binary works fine without any problem. Thanks, Taimoor On Thu, Aug 29, 2013 at 1:28 PM, Stefan Hajnoczi <stefa...@gmail.com> wrote: > On Thu, Aug 29, 2013 at 12:10:48AM +0500, Taimoor Mirza wrote: >> Hi Stefan, >> >> Below is result of bt: >> >> Breakpoint 1, 0x006ac304 in abort () >> (gdb) bt >> #0 0x006ac304 in abort () >> #1 0x00553052 in _fu10846____stack_chk_guard () at qemu-coroutine.c:111 >> #2 0x0040d746 in _fu473____stack_chk_guard () at block.c:4294 >> #3 0x00413cc7 in _fu805____stack_chk_guard () at block.c:2530 >> #4 0x00413cc7 in _fu805____stack_chk_guard () at block.c:2530 >> #5 0x00414875 in bdrv_rw_co_entry (opaque=0xa90f8d8) at block.c:2172 >> #6 _fu836____stack_chk_guard () at block.c:2167 >> #7 0x004439f8 in _fu1936____stack_chk_guard () at coroutine-win32.c:57 >> #8 0x767dbff2 in KERNEL32!GetQueuedCompletionStatus () >> from C:\windows\syswow64\kernel32.dll >> #9 0x035e3be8 in ?? () >> #10 0x767dbfaa in KERNEL32!GetQueuedCompletionStatus () >> from C:\windows\syswow64\kernel32.dll >> #11 0x019c3c70 in ?? () >> Cannot access memory at address 0xa080000 >> (gdb) > > Great, thanks. Please post the exact git commit ID you have built, I'm > having trouble tracking down the line numbers in qemu.git/master: > > $ git rev-parse HEAD > > Stefan
