[vz-dev] Fw: Re: libcurl: resolver with HAVE_ALARM not thread safe?!

[Thorben Thuermer]

der steffen ist schuld!!!!!11!!11!11oneoneeleven

Begin forwarded message:
Date: Mon, 22 Oct 2012 22:45:46 +0200
From: Thorben Thuermer <r00t at constancy.org>
To: libcurl development <curl-library at cool.haxx.se>
Subject: Re: libcurl: resolver with HAVE_ALARM not thread safe?!

> > i'm not sure if this is a libcurl bug or just a documentation issue,
> > but it has cost us some time to track down...
> 
> This is from curl_easy_setopt(3) 
> http://curl.haxx.se/libcurl/c/curl_easy_setopt.html
> 
> CURLOPT_NOSIGNAL
> 
>     Pass a long. If it is 1, libcurl will not use any functions that install
>     signal handlers or any functions that cause signals to be sent to the
>     process. This option is mainly here to allow multi-threaded unix
>     applications to still set/use all timeout options etc, without risking
>     getting signals. (Added in 7.10)
> 
> And this is from libcurl-tutorial(3)
> http://curl.haxx.se/libcurl/c/libcurl-tutorial.html#Multi-threading
> 
>     When using multiple threads you should set the CURLOPT_NOSIGNAL option
>     to 1 for all handles. 

ok, so it is documented, just not where i was looking
(i was looking for resolver-related issues after seeing the backtrace).
i did not write the application itself, i'll blame the original developer
for not reading the provided documentation on threaded usage. ;)