Congrats!
You guys have really made good job on making this happen!
//Jonas
After reading the thread on kernel I switched from libc_r to libthread_xu.
Now I have sporadic problems with a program that creates a thread to call
getaddrinfo(3). From time to time I get EAI_NODATA even though the address
is resolvable. It seems to be some timing issue as additional printfs make
Johannes Hofmann [EMAIL PROTECTED] wrote:
After reading the thread on kernel I switched from libc_r to libthread_xu.
Now I have sporadic problems with a program that creates a thread to call
getaddrinfo(3). From time to time I get EAI_NODATA even though the address
is resolvable. It seems to
:
:Never mind. The main thread seems to close fd 4 twice which interfers
:with getaddrinfo () in the other thread.
:
:Cheers,
:Johannes
:
:PS: ktrace is really great for debugging such stuff!
Excellent, glad I didn't have to try to track that one down!
libthread_xu is going to have
