CURLE_OK or CURLE_OUT_OF_MEMORY. Add typecast in hostares.c.
operation to the caller. Disconnecting has the disadvantage that the conn pointer gets completely invalidated and this is not handled on lots of places in the code.
produce a zlib error.
…se too many third-party libs and tools have problems. When curl is built without --disable-shared, the testing is done with a front-end script which makes the valgrind testing include (ba)sh as well and that often causes valgrind errors. Either we improve the valgrind error scanner a lot to better identify (lib)curl errors only, or we disable valgrind checking by default
…since the buffer is already BUFSIZE +1 one big to fit the extra trailing zero. This change is reported to fix David's weird SSL problem...
prevent memory leakage
… that it previously didn't detect and report the "Conditional jump or move depends on uninitialised value(s)" error. When I fixed this, I caught a few curl bugs with it. And then I had to spend time to make the test suite IGNORE these errors when OpenSSL is used since it produce massive amounts of valgrind warnings (but only of the "Conditional..." kind it seems). So, if a test that requires SSL is run, it ignores the "Conditional..." errors, and you'll get a "valgrind PARTIAL" output instead of "valgrind OK".
properly, to avoid reading uninited variables when using file:// (valgrind)
uninitialized variables. Pointed out to us by the friendly Valgrind.
…that gets closed just after the request has been sent failed and did not re-issue a request on a fresh reconnect like the easy interface did. Now it does! (define CURL_MULTIEASY, run test case 160)
…form() that uses the multi interface to run the request. It is a great testbed for the multi interface and I believe we shall do it this way for real in the future when we have a successor to curl_multi_fdset().
…ollowed" libcurl leaked the last Location: URL.
…ect() timed out" even though the reason was different. Fixed this problem by not setting this timeout to zero when using multi.