On Thu, 9 Sep 2010, Gautam Gopinadhan wrote:

>> I don't think so. The function is meant to use 'connp' further down when it
>> calls Curl_connect() and that's the function that is supposed to update
>> that variable. But I can't tell with 100% certainty...
>
> Thanks.. Though (to my rather naive eyes) it looked like if Curl_done()
> returns an error in this context, the contents of connp will hold a stale
> pointer and a check in transfer.c ends up referring to the stale data.

I'm sorry but I get lost in this. Can you please check the latest source code
and see if you spot the same flaw you see and explain it for me again?

I don't see how Curl_done() can return an error with a bad pointer in *connp.

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html