#18697 [Fbk-Opn]: HTTPS POST crashing
ID: 18697 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Feedback +Status: Open Bug Type: cURL related Operating System: Linux PHP Version: 4.2.3 New Comment: Because this PHP/curl is on a production server with 200 websites, it's not that easy to get a chance to re-compile stuff without breaking scripts. I will re-compile curl with debug symbols at some point over the next few days. For your information: a curl HTTPS POST works fine from the command line. Previous Comments: [2002-10-12 09:46:43] [EMAIL PROTECTED] Compile curl also with debug symbols enabled.. [2002-10-12 09:46:19] [EMAIL PROTECTED] Thank you for this bug report. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://bugs.php.net/bugs-generating-backtrace.php Once you have generated a backtrace, please submit it to this bug report and change the status back to Open. Thank you for helping us make PHP better. As you can see, the bug is in curl itself. [2002-10-12 03:05:22] [EMAIL PROTECTED] Tried CVS snapshop but got exactly the same crash: (gdb) run -X Starting program: /usr/sbin/httpd -X (no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x in ?? () (gdb) bt #0 0x in ?? () #1 0x40512813 in RAND_add () from /usr/local/lib/libcurl.so.2 Cannot access memory at address 0x4000 [2002-10-12 02:21:37] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip [2002-10-12 02:10:12] [EMAIL PROTECTED] For your information, this is with libcurl 7.9.8 (OpenSSL 0.9.6). The crashes occur when POSTing to a https URL. curl works fine from the command line. Here is the backtrace output from gdb: Starting program: /usr/sbin/httpd -X (no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x in ?? () (gdb) bt #0 0x in ?? () #1 0x4048e813 in RAND_add () from /usr/local/lib/libcurl.so.2 Cannot access memory at address 0x4000 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/18697 -- Edit this bug report at http://bugs.php.net/?id=18697edit=1
#18697 [Fbk-Opn]: HTTPS POST crashing
ID: 18697 User updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Feedback +Status: Open Bug Type: cURL related Operating System: Linux PHP Version: 4.2.3 New Comment: Tried CVS snapshop but got exactly the same crash: (gdb) run -X Starting program: /usr/sbin/httpd -X (no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x in ?? () (gdb) bt #0 0x in ?? () #1 0x40512813 in RAND_add () from /usr/local/lib/libcurl.so.2 Cannot access memory at address 0x4000 Previous Comments: [2002-10-12 02:21:37] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php4-latest.tar.gz For Windows: http://snaps.php.net/win32/php4-win32-latest.zip [2002-10-12 02:10:12] [EMAIL PROTECTED] For your information, this is with libcurl 7.9.8 (OpenSSL 0.9.6). The crashes occur when POSTing to a https URL. curl works fine from the command line. Here is the backtrace output from gdb: Starting program: /usr/sbin/httpd -X (no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x in ?? () (gdb) bt #0 0x in ?? () #1 0x4048e813 in RAND_add () from /usr/local/lib/libcurl.so.2 Cannot access memory at address 0x4000 [2002-09-26 19:51:00] [EMAIL PROTECTED] No feedback was provided. The bug is being suspended because we assume that you are no longer experiencing the problem. If this is not the case and you are able to provide the information that was requested earlier, please do so and change the status of the bug back to Open. Thank you. [2002-09-09 05:35:46] [EMAIL PROTECTED] Thank you for this bug report. To properly diagnose the problem, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://bugs.php.net/bugs-generating-backtrace.php Once you have generated a backtrace, please submit it to this bug report and change the status back to Open. Thank you for helping us make PHP better. [2002-09-09 05:31:19] [EMAIL PROTECTED] Well, just try it without... Derick 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/18697 -- Edit this bug report at http://bugs.php.net/?id=18697edit=1
