From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LiSls-0000Z8-Vt for qemu-devel@nongnu.org; Sat, 14 Mar 2009 08:15:21 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LiSln-0000XZ-4U for qemu-devel@nongnu.org; Sat, 14 Mar 2009 08:15:19 -0400 Received: from [199.232.76.173] (port=48083 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LiSlm-0000XW-VW for qemu-devel@nongnu.org; Sat, 14 Mar 2009 08:15:15 -0400 Received: from mail.gmx.net ([213.165.64.20]:58050) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1LiSlm-0003QR-Cp for qemu-devel@nongnu.org; Sat, 14 Mar 2009 08:15:14 -0400 Date: Sat, 14 Mar 2009 13:16:58 +0100 (CET) From: Johannes Schindelin Subject: Re: [Qemu-devel] Re: SIGSEGV on Windows with KQEMU enabled In-Reply-To: Message-ID: References: <49B1E13C.9060900@codemonkey.ws> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Consul Cc: qemu-devel@nongnu.org Hi, On Fri, 13 Mar 2009, Consul wrote: > Johannes Schindelin wrote: > > > compiling with --std=c99? > > with -std=c99 it does not even compile ... error message? > > Alternatively, you might want to try to > > > > #define snprintf __mingw_snprintf > > #define vsnprintf __mingw_vsnprintf > > > > These give linker undefined symbol errors. ... error message? And further: do you use the TDM GCC4? > But really funny think is the change that triggers the bug is precisely this: > -Monitor *cur_mon; > +Monitor *cur_mon = NULL; > > Obviously, kqemu is happier having garbage in the cur_mon than NULL I rather expect that to _hide_ the bug. The "garbage" might be a left-over from the heap. Ciao, Dscho