This is the mail archive of the
libc-hacker@cygnus.com
mailing list for the glibc project.
Re: [Patch]: SIGSEGV: exceptions with thread specific data
- To: hjl@varesearch.com
- Subject: Re: [Patch]: SIGSEGV: exceptions with thread specific data
- From: Wolfram Gloger <wmglo@dent.med.uni-muenchen.de>
- Date: 16 Mar 1999 22:01:15 -0000
- CC: jason@cygnus.com, Wolfram.Gloger@dent.med.uni-muenchen.de, libc-hacker@cygnus.com
- References: <m10MzsF-000AUbC@shanghai.varesearch.com>
> > 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