ID: 36862 Updated by: [EMAIL PROTECTED] Reported By: nick at sterlingintegrated dot com -Status: Open +Status: Feedback Bug Type: MySQL related Operating System: Fedora Core 3 (FC3) PHP Version: 5.1.2 New Comment:
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 for *NIX and http://bugs.php.net/bugs-generating-backtrace-win32.php for Win32 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. Previous Comments: ------------------------------------------------------------------------ [2006-03-26 12:19:57] nick at sterlingintegrated dot com Description: ------------ After an upgrade of MySQL from 3.23 to 4.0, I kept getting "mysql_connect not a valid function call". So I recompiled php. Then I got a blank scrren on the browser. When run, "~php ./test.php" produces an error message (which can't be seen in the browser). The solution for me was to "export MALLOC_CHECK=0;" on the command line, so glibc stops going crazy then restart httpd. I set this env variable in my .bash_profile. It seems to work fine so far. Reproduce code: --------------- <?php error_reporting(E_ALL); $link = mysql_connect('localhost', 'user', 'password'); if (!$link) { die('Could not connect: ' . mysql_error()); } echo 'Connected successfully'; mysql_close($link); ?> Expected result: ---------------- Connected successfully Actual result: -------------- *** glibc detected *** double free or corruption ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=36862&edit=1
