From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GEDJr-0003tV-9A for qemu-devel@nongnu.org; Fri, 18 Aug 2006 19:00:03 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GEDJq-0003sf-BX for qemu-devel@nongnu.org; Fri, 18 Aug 2006 19:00:02 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GEDJq-0003sc-8g for qemu-devel@nongnu.org; Fri, 18 Aug 2006 19:00:02 -0400 Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1GEDQe-0003pW-0P for qemu-devel@nongnu.org; Fri, 18 Aug 2006 19:07:04 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GEDJe-00038e-QQ for qemu-devel@nongnu.org; Sat, 19 Aug 2006 00:59:50 +0200 Received: from host.ci.hillsboro.or.us ([4.18.224.6]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 19 Aug 2006 00:59:50 +0200 Received: from void by host.ci.hillsboro.or.us with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 19 Aug 2006 00:59:50 +0200 From: "alex" Date: Fri, 18 Aug 2006 15:59:35 -0700 Message-ID: Sender: news Subject: [Qemu-devel] infinite loop at startup on windows Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi, I've been using QEMU for some time now, and am very pleased with it. Thank you for the great product. However, it seems to me that current CVS version (at least on Windows XP host) is entering into an infinite loop at startup, eating 97% of the CPU power. On the title it shows QEMU [Stopped], and opens the Monitor view, but does not respond to any input. I could not run any of my old (qcow, if that matters) images; interestingly, I was able to run the Debian installer from a CD image (blank qcow hd image), but was not able to boot neither from the hard drive image nor from the cd after install had been complete. When I attach the debugger, I always get the similar result (below). Does this make sense to you? Thank you, Alex. (gdb) where #0 0x77f813b2 in ntdll!DbgUiConnectToDbg () from C:\WINNT\system32\NTDLL.DLL #1 0x7c57fe8f in KERNEL32!DebugActiveProcess () from C:\WINNT\system32\KERNEL32.DLL #2 0x7c57b388 in lstrcmpiW () from C:\WINNT\system32\KERNEL32.DLL #3 0x00000000 in ?? () from #4 0x00000000 in ?? () from #5 0x00000000 in ?? () from #6 0x7ffdc000 in ?? () #7 0x00000000 in ?? () from #8 0x00b3ffc0 in code_gen_buffer () (gdb) Cannot access memory at address 0x7195c0 Windows XP Pro MINGW32_NT-5.0 WC08326 1.0.10(0.46/3/2) 2004-03-15 07:17 gcc.exe (GCC) 3.4.2 (mingw-special)