[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Re: SIGSEGV on Windows with KQEMU enabled
From: |
Johannes Schindelin |
Subject: |
Re: [Qemu-devel] Re: SIGSEGV on Windows with KQEMU enabled |
Date: |
Sat, 14 Mar 2009 13:16:58 +0100 (CET) |
User-agent: |
Alpine 1.00 (DEB 882 2007-12-20) |
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
- [Qemu-devel] SIGSEGV on Windows with KQEMU enabled, Consul, 2009/03/06
- Re: [Qemu-devel] SIGSEGV on Windows with KQEMU enabled, Anthony Liguori, 2009/03/06
- [Qemu-devel] Re: SIGSEGV on Windows with KQEMU enabled, Consul, 2009/03/12
- Re: [Qemu-devel] Re: SIGSEGV on Windows with KQEMU enabled, Johannes Schindelin, 2009/03/13
- [Qemu-devel] Re: SIGSEGV on Windows with KQEMU enabled, Consul, 2009/03/13
- Re: [Qemu-devel] Re: SIGSEGV on Windows with KQEMU enabled,
Johannes Schindelin <=
- Re: [Qemu-devel] Re: SIGSEGV on Windows with KQEMU enabled, Andreas Färber, 2009/03/14
- Re: [Qemu-devel] Re: SIGSEGV on Windows with KQEMU enabled, Paul Brook, 2009/03/14
- Re: [Qemu-devel] Re: SIGSEGV on Windows with KQEMU enabled, Stefan Weil, 2009/03/15
- Re: [Qemu-devel] Re: SIGSEGV on Windows with KQEMU enabled, Avi Kivity, 2009/03/15
- Re: [Qemu-devel] Re: SIGSEGV on Windows with KQEMU enabled, Johannes Schindelin, 2009/03/16