libcurl: resolver with HAVE_ALARM not thread safe?!

2012-10-22 Thread Thorben Thuermer
Hello, on http://curl.haxx.se/libcurl/features.html we find: libcurl is designed and implemented entirely thread safe. libcurl uses certain system calls to obtain information. Some of the most crucial ones are the name resoluition calls (the gethostby* family). i just debugged a problem in a

Re: libcurl: resolver with HAVE_ALARM not thread safe?!

2012-10-22 Thread Dan Fandrich
On Mon, Oct 22, 2012 at 02:24:01AM +0200, Thorben Thuermer wrote: on http://curl.haxx.se/libcurl/features.html we find: libcurl is designed and implemented entirely thread safe. libcurl uses certain system calls to obtain information. Some of the most crucial ones are the name resoluition

Re: libcurl: resolver with HAVE_ALARM not thread safe?!

2012-10-22 Thread Thorben Thuermer
On Mon, 22 Oct 2012 22:07:16 +0200 Dan Fandrich d...@coneharvesters.com wrote: On Mon, Oct 22, 2012 at 02:24:01AM +0200, Thorben Thuermer wrote: on http://curl.haxx.se/libcurl/features.html we find: libcurl is designed and implemented entirely thread safe. libcurl uses certain system calls

Re: libcurl: resolver with HAVE_ALARM not thread safe?!

2012-10-22 Thread Daniel Stenberg
On Mon, 22 Oct 2012, Thorben Thuermer wrote: alarm() is called even when connecting to numeric IP addresses, Room for improvement there I'd say! libcurl now gives a number of choices of DNS resolver back-end at compile time, some of which are immune to this problem. yes, i found those.