2010/4/13 Timo Teräs timo.te...@iki.fi:
It looks like no one bothered to implement the uClibc needed stdio
locking initialization. It seems that only linuxthreads.old does this.
So both linuxthreads.new and nptl seem to be broken wrt. stdio locking.
ah. yes.
I did not even try compile
Hi,
something is definitively wrong with stdio used in threads on x86.
I have enabled run-time assertions and run this phello.c on a multicore box:
#include pthread.h
#include stdio.h
void * printmsg(char *s){
printf(printmsg: %s\n, s);
return;
}
void pthread_hello(void)
{
On 04/12/2010 12:21 PM, Natanael Copa wrote:
Smells like stdio is not threads safe?
Interesting. I supposed there could be an issue with the libc internal futex
code that replaces the old use of pthread mutexes directly. We could verify this
with a bit of work by getting the old style mutexes to
Austin Foxley wrote:
On 04/12/2010 12:21 PM, Natanael Copa wrote:
Smells like stdio is not threads safe?
Interesting. I supposed there could be an issue with the libc internal futex
code that replaces the old use of pthread mutexes directly. We could verify this
with a bit of work by getting
