|
Boost : |
Subject: Re: [boost] Thread (win32) and current_thread_tls_key issues
From: Pekka Seppänen (pekka.seppanen_at_[hidden])
Date: 2012-07-03 03:53:05
On 3.7.2012 10:39, Anthony Williams wrote:
> On 02/07/12 09:50, Pekka Seppänen wrote:
>> Currently Threads's Win32 TLS implementation uses a global static variable
>> thread::current_thread_tls_key that is defined in src/win32/thread.cpp. As you
>> may know, static variables have a tendency of not being allocated in a very
>> specific order.
>
> Oops. This was changed from direct init via a macro (which does lead to
> static initialization) to init via an intermediate variable (which
> doesn't) in the recent batch of thread updates and I didn't spot it.
>
> I'll commit a fix for it.
>
/o\
Argh, of course that's the real problem why this was occurring in the first
place. I wonder how could I miss that one especially when I've been lately
patching some internal (static) values of a certain 3rd party DLLs.
Should've spotted that. Well, no harm was luckily done even my proposed cure
was worse than the disease this time..
-- Pekka
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk