[Patch]: SIGSEGV: exceptions with thread specific data
Wolfram Gloger
wmglo@dent.med.uni-muenchen.de
Tue Mar 16 14:01:00 GMT 1999
> > What is the problem, exactly? Why can't we share malloced memory between
> > threads?
> >
>
> I don't know for sure. Maybe Wolfram knows. It may be a bug in glibc.
glibc's malloc is most definitely thread-safe, as long as it
is properly initialized. Do the malloc() requests for exception
handling happen very early, maybe even before glibc's constructors
have run ?
I'll have more time to look into this later this week. If someone
can send me the latest test-case, I'd be grateful
Regards,
Wolfram.
--
`Surf the sea, not double-u three...'
wmglo@dent.med.uni-muenchen.de
More information about the Libc-hacker
mailing list