On Fri, Sep 19, 2003 at 12:59:53AM +0100, Philip Blundell wrote: > On Fri, 2003-09-19 at 00:54, Daniel Jacobowitz wrote: > > I think the real answer has to be "don't do that". Every use of this > > idiom breaks with dlopen. This is the worst offender but I'm betting > > there are others. __pthread_setspecific seems to be one. > > Mmm. I'm not sure that outlawing the use of libpthread (or any library > linked with pthreads, which also means stuff like librt) in any object > that might potentially be dlopen()d is a tenable position. > > I wonder why this problem has only started happening recently, though.
Didn't used to use cancellation for any locking. Only syslog does now, IIRC, or only syslog did until very recently. > > Ask libc-alpha? > > Yeah, probably best. > > p. > > -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
