#48203 [Ver]: crash when CURLOPT_STDERR is set to regular file

ID: 48203 User updated by: php-bug at paulsohier dot nl Reported By: php-bug at paulsohier dot nl Status: Verified Bug Type: cURL related Operating System: * PHP Version: 5.*, 6CVS (2009-05-09) New Comment: We just tried it with some more different hosts, and it happens at at least google.nl and nu.nl as well. Also, adding the curl_close() to the end fixs the problem. But should php's GC not do the same call internally? Previous Comments: ------------------------------------------------------------------------ [2009-05-09 21:30:58] jani@php.net Mark: CURLOPT_STDERR Pass a FILE * as parameter. Tell libcurl to use this stream instead of stderr when showing the progress meter and displaying CURLOPT_VERBOSE data. ------------------------------------------------------------------------ [2009-05-09 21:30:12] jani@php.net Adding this as last line also fixes the problem (ie. reset to default..) curl_setopt($ch, CURLOPT_STDERR, STDERR); I don't know why the other hosts work and other don't. Propably there's some traffic / error and the file handle gets destroyed or otherwise mangled during shutdown and curl then tries to use it.. ------------------------------------------------------------------------ [2009-05-09 21:23:40] mark at dynom dot nl I can reproduce it on cURL 7.19.4 on PHP 5.2.9, but only when not using the verbose option. When CURLOPT_VERBOSE is false, or not set at all, I get no segfaults. When true, it segfaults. ------------------------------------------------------------------------ [2009-05-09 20:58:11] php-bug at paulsohier dot nl Its also related somehow to the url thats used to fetch, as when you try it with example.org the script works okay. ------------------------------------------------------------------------ [2009-05-09 20:51:47] jani@php.net Verified with all branches using cURL 7.15.5 ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/48203 -- Edit this bug report at http://bugs.php.net/?id=48203&edit=1