Date: Mon, 21 Oct 2002 14:03:52 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Linus Kendall <linus@angliaab.se> Cc: Peter Pentchev <roam@ringlet.net>, freebsd-hackers@FreeBSD.ORG Subject: Re: PThreads problem Message-ID: <3DB46BB8.46401DF5@mindspring.com> References: <1035200159.24315.13.camel@bilbo> <20021021124520.GS389@straylight.oblivion.bg> <1035206648.24315.20.camel@bilbo> <20021021134834.GA41198@straylight.oblivion.bg> <20021021135045.GB41198@straylight.oblivion.bg> <1035218026.24330.33.camel@bilbo> <20021021194453.GB377@straylight.oblivion.bg> <1035232308.24315.37.camel@bilbo>
next in thread | previous in thread | raw e-mail | index | archive | help
Linus Kendall wrote: > That was very thorough, thanks! Now I at least have a notion of what > is going on. Since this is slightly urgent I guess a hack into the > libcurl source code to try to remove the sigalarms would do the trick > (in my case). In the general case it seems like there's a rather big > problem here as libcurl's behavior cannot really work together with the > FreeBSD implementation of threads. It is more correct to say that libcurl makes an assumption about signal delivery which is not guaranteed by POSIX, and therefore libcurl will not work with *any* POSIX compliant threads implementation which does not *happen* to work this way. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DB46BB8.46401DF5>