In fact I did not set CURLOPT_NOSIGNAL, which is my bad. After setting it the problem also went away even if I did not restore the signal handler.

In case CURLOPT_NOSIGNAL is not set, is it not supposed to change any signal handler after the curl_easy_perform? As of now I'm still not sure if this is a bug or not.

Thanks
andy

-----Original Message-----
From: curl-library-bounces_at_cool.haxx.se
[mailto:curl-library-bounces_at_cool.haxx.se]On Behalf Of Daniel Stenberg
Sent: Thursday, July 14, 2005 11:47 PM
To: libcurl development
Subject: RE: libcurl in JNI context

On Thu, 14 Jul 2005, Lai, Andy wrote:

> The signal handler for SIGPIPE is changed after the curl_easy_perform call
> to a default one, which happens to kill the process.
>
> I fixed it by saving the current signal handler before curl_easy_perform and
> then restore it after. The problem then went away.

Are you saying that curl_easy_perform() removed your signal handler or that
this is some kind of libcurl bug at least?

Are you using CURLOPT_NOSIGNAL ?

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html