[uClibc]Thread-safeness

[Erik Andersen]

On Mon Apr 23, 2001 at 12:52:56PM +0300, Michael Shmulevich wrote:
> > 
> > We aim to make it thread safe and include thread safe versions of inherently
> > thread unsafe functions.  So it _should_ be thread safe, but I don't know of
> > any explicit testing that has been done to test/verify the thread safety.
> > 
> >  -Erik
> 
> I am currently trying to add pthreads support to uclibc, but don't see 
> how to do it exactly. In glibc it is built as a part of glibc's tree, 
> and I didn't succed in bringing the sources to be compatible with 
> uclibc. There are many parts, like linuxthreads_db, that are completely 
> missing from uclibc.
> 
> Erik, if you already started working on this, please enlighten me how 
> did you plan to do it. I saw several mentions of "pthread" all over 
> bits/ files, but seen no implementation, not even scheduling syscalls.

To be honest, I havn't even started working on this.  I've been 
trying to make functions reentrant (or add reentrant alternatives
when the interface is inherently thread-unsafe), but I have not
even begun working on porting pthreads to uClibc.

Right now I am working on the shared lib loader to get rid of
as much asm as possible.

 -Erik

--
Erik B. Andersen   email:  andersen at lineo.com
--This message was written using 73% post-consumer electrons--