Found a bug in how pointers are handled when dealing with file URLs.
Specifically, in file.c:Curl_file_connect, if the incomming URL is in the
form file:///c:/whatever CURL increments the pointer by one (line 143). But
since this is dynamically allocated memory, the new pointer is no longer
valid and the subsequent call to free fails (either its silently ignored
resulting in a leak, or crashes if strict checking of memory allocs/frees is
enabled.)

BTW - we're using the new memory callbacks which helped track this down :)
Received on 2004-06-10