Re: (glibc-2.0.7) c++ constructors and pthreads

[Wolfram Gloger <wmglo@dent.med.uni-muenchen.de>]

> I have a crash case here for a program which has global c++
> constructors and links against linuxthreads, one of the c++
> constructors ends up calling malloc(), and this crashes because the
> pthread constructor has not run yet

That's strange, on the very first call, malloc() calls ptmalloc_init()
via the initial special hooks, which in turn calls
__pthread_initialize() if that symbol has been linked in.  Can you
check why this is not working ?

> and malloc() wants to setup it's
> internal locks in the private area of the pthread_initial_thread.

You mean it wants to set up a thread-specific data key, right ?  This,
too, happens after the call to __pthread_initialize(), so I don't see
why it should cause a problem.

> This is deadly on machines such as Sparc which have to do
> INIT_THREAD_SELF to initialize a global register to point to the
> thread information block.

This should happen somewhere in/via __pthread_initialize(),
shouldn't it ?

Regards,
Wolfram.
-- 
`Surf the sea, not double-u three...'
wmglo@dent.med.uni-muenchen.de