On Fri, 2009-11-20 at 14:09 -0500, Dan Winship wrote:
> On 11/20/2009 01:49 PM, Alexander Larsson wrote:
> > What about making g_slice able to handle late initialization of threads,
> > but everything else that uses g_thread apis to protect something would
> > just get threads auto-initialized. The
On 11/20/2009 01:49 PM, Alexander Larsson wrote:
> What about making g_slice able to handle late initialization of threads,
> but everything else that uses g_thread apis to protect something would
> just get threads auto-initialized. Then super-simple apps using just
> glist and ghashtable would no
On Fri, 2009-11-20 at 15:27 +, Michael Meeks wrote:
> On Fri, 2009-11-20 at 14:02 +0100, Alexander Larsson wrote:
> > > it was fixed a very long time ago. The problem, as you note, is with
> > > everything above libglib in the stack, not with libglib itself.
> >
> > We really need to get our st
On Fri, 2009-11-20 at 14:02 +0100, Alexander Larsson wrote:
> > it was fixed a very long time ago. The problem, as you note, is with
> > everything above libglib in the stack, not with libglib itself.
>
> We really need to get our story together here. Either we do our very
> best to handle late g_
On Fri, Nov 20, 2009 at 11:27 AM, Tor Lillqvist wrote:
>> We really need to get our story together here. Either we do our very
>> best to handle late g_thread_init(), or we should fail spectactularly.
>
> Agree 100%.
>
> My own humble opinion is that even GLib (not just GIO) should link to
> -lpth
On Fri, 2009-11-20 at 14:23 +0100, nf2 wrote:
> Hmm - i still wonder how many milliseconds putting everything into
> libgio.so rather than having three separate libraries will really safe
> you.
While symbol resolution is important, I actually don't think it's the
main reason we want everything in
> We really need to get our story together here. Either we do our very
> best to handle late g_thread_init(), or we should fail spectactularly.
Agree 100%.
My own humble opinion is that even GLib (not just GIO) should link to
-lpthread and work as if g_thread_init(NULL) would have been
implicitly
On Tue, Nov 17, 2009 at 10:52 AM, Alexander Larsson wrote:
> On Fri, 2009-11-13 at 16:37 +0200, Andrew W. Nosenko wrote:
>> On Fri, Nov 13, 2009 at 15:31, Alexander Larsson wrote:
>> > On Fri, 2009-11-13 at 01:31 +0200, Andrew W. Nosenko wrote:
>> >> On Thu, Nov 12, 2009 at 20:52, Alexander Larss
On Wed, 2009-11-18 at 11:56 -0500, Dan Winship wrote:
> On 11/18/2009 11:17 AM, Tristan Van Berkom wrote:
> > While the GSlice allocator storing some per-thread data and getting messed
> > up across g_thread_init() might be a fixable bug
>
> it was fixed a very long time ago. The problem, as you n
