Bug#175511: errno is mishandled by libc in multithreaded programs
On Tue, Jan 07, 2003 at 04:39:18PM +0000, Nikita Schmidt wrote:
> I've observed the same symptoms trying to run a multithreaded application
> linked with libcurl: libcurl can't connect to a remote server. This
> happens under both -8 and -9.
> The following erroneous behaviour has been sighted: after calling a
> syscall that returns an error, errno is often found to be 0 in
> multithreaded programs. This causes connection failures in libcurl and
> probably in mozilla and galeon as well.
Libcurl correctly uses __errno_location(); I assume the others do also.
That makes the failure quite surprising. Can you produce a test case
MontaVista Software Debian GNU/Linux Developer