#47283 [Bgs]: mysql_connect call crashes web server
ID: 47283 User updated by: darren at misterdoom dot com Reported By: darren at misterdoom dot com Status: Bogus Bug Type: MySQL related Operating System: win32 only - Vista Home Premium PHP Version: 5.2.8 Assigned To: pajoye New Comment: I used the PHP supplied DLLS. The PHP extensions directory is in the path information, the MySQL DLL was visible. This problem happened with IIS 7, not just Apache. Thinking about it logically, if the DLL was not visible or the incorrect DLL with the 5.2.8 install, it would have still not been visible or correct with the 5.2.5 install, which is working. This is a bug, not bogus. Previous Comments: [2009-02-10 18:40:45] paj...@php.net Do not ever use DLLs from mysql but only the one we provide with PHP. Be sure that PHP's install directory (where the libmysql.dll is) is first in your path for apache. Not a php bug bogus. [2009-02-10 10:44:18] tony2...@php.net Pierre, you seem to know what's wrong there - is this some lib version incompatibility? [2009-02-06 22:44:57] darren at misterdoom dot com Yes, I am running MySql 5.1.11. I have un-installed PHP 5.2.8 as I needed to continue working on my web site. I now have PHP 5.2.5 installed, and the problem does not occur. [2009-02-06 13:46:53] paj...@php.net And you have installed mysql 5.1 right? [2009-02-06 13:25:57] ka...@php.net 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. 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/47283 -- Edit this bug report at http://bugs.php.net/?id=47283edit=1
#47283 [Bgs]: mysql_connect call crashes web server
ID: 47283 Updated by: paj...@php.net Reported By: darren at misterdoom dot com Status: Bogus Bug Type: MySQL related Operating System: win32 only - Vista Home Premium PHP Version: 5.2.8 Assigned To: pajoye New Comment: Please, read again what I said. There is dozen other reports about this exact issue with detailed explanations. Take a look at them. Previous Comments: [2009-02-11 09:20:17] darren at misterdoom dot com I used the PHP supplied DLLS. The PHP extensions directory is in the path information, the MySQL DLL was visible. This problem happened with IIS 7, not just Apache. Thinking about it logically, if the DLL was not visible or the incorrect DLL with the 5.2.8 install, it would have still not been visible or correct with the 5.2.5 install, which is working. This is a bug, not bogus. [2009-02-10 18:40:45] paj...@php.net Do not ever use DLLs from mysql but only the one we provide with PHP. Be sure that PHP's install directory (where the libmysql.dll is) is first in your path for apache. Not a php bug bogus. [2009-02-10 10:44:18] tony2...@php.net Pierre, you seem to know what's wrong there - is this some lib version incompatibility? [2009-02-06 22:44:57] darren at misterdoom dot com Yes, I am running MySql 5.1.11. I have un-installed PHP 5.2.8 as I needed to continue working on my web site. I now have PHP 5.2.5 installed, and the problem does not occur. [2009-02-06 13:46:53] paj...@php.net And you have installed mysql 5.1 right? 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/47283 -- Edit this bug report at http://bugs.php.net/?id=47283edit=1
#47283 [Bgs]: mysql_connect call crashes web server
ID: 47283 User updated by: darren at misterdoom dot com Reported By: darren at misterdoom dot com Status: Bogus Bug Type: MySQL related Operating System: win32 only - Vista Home Premium PHP Version: 5.2.8 Assigned To: pajoye New Comment: I have read what you said, and it from my understanding, you are saying that my install was either not finding the dll, or finding the incorret dll because the path information is incorrect. It also seemed to relate only to Apache I ask, if that is the case, then why does it work after uninstalling 5.2.8 and installing 5.2.5 without any path information changing? Also, the problem was present in both Apache and IIS 7. I did search for the error, however most of the answers that I could see pointed the error at a bad version of the ISAPI dll. Previous Comments: [2009-02-11 09:26:07] paj...@php.net Please, read again what I said. There is dozen other reports about this exact issue with detailed explanations. Take a look at them. [2009-02-11 09:20:17] darren at misterdoom dot com I used the PHP supplied DLLS. The PHP extensions directory is in the path information, the MySQL DLL was visible. This problem happened with IIS 7, not just Apache. Thinking about it logically, if the DLL was not visible or the incorrect DLL with the 5.2.8 install, it would have still not been visible or correct with the 5.2.5 install, which is working. This is a bug, not bogus. [2009-02-10 18:40:45] paj...@php.net Do not ever use DLLs from mysql but only the one we provide with PHP. Be sure that PHP's install directory (where the libmysql.dll is) is first in your path for apache. Not a php bug bogus. [2009-02-10 10:44:18] tony2...@php.net Pierre, you seem to know what's wrong there - is this some lib version incompatibility? [2009-02-06 22:44:57] darren at misterdoom dot com Yes, I am running MySql 5.1.11. I have un-installed PHP 5.2.8 as I needed to continue working on my web site. I now have PHP 5.2.5 installed, and the problem does not occur. 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/47283 -- Edit this bug report at http://bugs.php.net/?id=47283edit=1
#47283 [Bgs]: mysql_connect call crashes web server
ID: 47283 Updated by: paj...@php.net Reported By: darren at misterdoom dot com Status: Bogus Bug Type: MySQL related Operating System: win32 only - Vista Home Premium PHP Version: 5.2.8 Assigned To: pajoye New Comment: In your setup, PHP uses libmysql.dll from mysql 5.1, and that's why it crashes, I'm 99.999% sure about that. Try php.exe using CLI from a command line: cd c:\php528 php -dextension_dir=ext -dextension=php_mysql.dll mysql.php and it will work smoothly. Previous Comments: [2009-02-11 10:28:00] darren at misterdoom dot com I have read what you said, and it from my understanding, you are saying that my install was either not finding the dll, or finding the incorret dll because the path information is incorrect. It also seemed to relate only to Apache I ask, if that is the case, then why does it work after uninstalling 5.2.8 and installing 5.2.5 without any path information changing? Also, the problem was present in both Apache and IIS 7. I did search for the error, however most of the answers that I could see pointed the error at a bad version of the ISAPI dll. [2009-02-11 09:26:07] paj...@php.net Please, read again what I said. There is dozen other reports about this exact issue with detailed explanations. Take a look at them. [2009-02-11 09:20:17] darren at misterdoom dot com I used the PHP supplied DLLS. The PHP extensions directory is in the path information, the MySQL DLL was visible. This problem happened with IIS 7, not just Apache. Thinking about it logically, if the DLL was not visible or the incorrect DLL with the 5.2.8 install, it would have still not been visible or correct with the 5.2.5 install, which is working. This is a bug, not bogus. [2009-02-10 18:40:45] paj...@php.net Do not ever use DLLs from mysql but only the one we provide with PHP. Be sure that PHP's install directory (where the libmysql.dll is) is first in your path for apache. Not a php bug bogus. [2009-02-10 10:44:18] tony2...@php.net Pierre, you seem to know what's wrong there - is this some lib version incompatibility? 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/47283 -- Edit this bug report at http://bugs.php.net/?id=47283edit=1
