On Tue, Oct 08, 2013 at 11:58:31AM +0200, Stefan Hajnoczi wrote:
> glib versions prior to 2.31.0 require an explicit g_thread_init() call
> to enable multi-threading.
>
> Failure to initialize threading causes glib to take single-threaded code
> paths without synchronization. For example, the g_s
On Tue, Oct 08, 2013 at 03:58:24PM +0200, Kevin Wolf wrote:
> Am 08.10.2013 um 15:08 hat Paolo Bonzini geschrieben:
> > Il 08/10/2013 14:25, Kevin Wolf ha scritto:
> > > The glib documentation says:
> > >
> > > Since version 2.24, calling g_thread_init() multiple times is
> > > allowed, bu
Am 08.10.2013 um 15:08 hat Paolo Bonzini geschrieben:
> Il 08/10/2013 14:25, Kevin Wolf ha scritto:
> > The glib documentation says:
> >
> > Since version 2.24, calling g_thread_init() multiple times is
> > allowed, but nothing happens except for the first call.
> >
> > I take that this m
Il 08/10/2013 14:25, Kevin Wolf ha scritto:
> The glib documentation says:
>
> Since version 2.24, calling g_thread_init() multiple times is
> allowed, but nothing happens except for the first call.
>
> I take that this means previously it wasn't allowed. qemu's configure
> checks for a m
Am 08.10.2013 um 11:58 hat Stefan Hajnoczi geschrieben:
> glib versions prior to 2.31.0 require an explicit g_thread_init() call
> to enable multi-threading.
>
> Failure to initialize threading causes glib to take single-threaded code
> paths without synchronization. For example, the g_slice allo
