myalarm() is history, we now use HAVE_ALARM and we now do our very best to

1 - restore the previous sigaction struct as soon as we are about to shut
off our timeout
2 - restore the previous alarm() timeout, in case an application or similar
had it running before we "borrowed" it for a while.

No, this does not fix the multi-thread problem you get with alarm(). This
patch should correct bug report #478780:
//sourceforge.net/tracker/?func=detail&atid=100976&aid=478780&group_id=976

If not, please post details!
This commit is contained in:
Daniel Stenberg
2001-11-06 19:33:13 +00:00
parent 3dfc509d33
commit 2e32d415c0
3 changed files with 82 additions and 40 deletions

View File

@@ -1159,10 +1159,6 @@ CURLcode Curl_perform(struct SessionHandle *data)
if(newurl)
free(newurl);
/* make absolutely sure the alarm is switched off! */
if(data->set.timeout || data->set.connecttimeout)
myalarm(0);
return res;
}