lock/unlock in newlib
Thu Aug 9 06:09:00 GMT 2001
I am curious if newlib has reached the point where providing
mutex interface code (*lock, *unlock) is sufficient to make it
thread safe. The documentation makes it look like it only covers
malloc and setenv/getenv which means the reentrancy structure
still has to be switched for other issues.
Is this correct? If lock/unlock covers everything, I would
like to use that mechanism.
Joel Sherrill, Ph.D. Director of Research & Development
joel@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
More information about the Newlib