ID: 35428 User updated by: marcing at smlw dot pl Reported By: marcing at smlw dot pl Status: Open Bug Type: MySQLi related Operating System: WinXP SP2 PHP Version: 5CVS-2005-11-28 (snap) New Comment:
I forgot i was running mysql 4.1.15:) The backtrace from php 5.1.2-dev and mysql 5.0.16: Program received signal SIGSEGV, Segmentation fault. 0x00e654de in ?? () (gdb) bt #0 0x00e654de in ?? () #1 0x00000021 in ?? () #2 0x00374128 in ?? () Previous Comments: ------------------------------------------------------------------------ [2005-11-28 15:21:39] marcing at smlw dot pl Now im sure its irrelevant, sorry. ------------------------------------------------------------------------ [2005-11-28 15:20:23] marcing at smlw dot pl I dont know if its relevant, but i get exactly the same gdb backtrace as here http://bugs.php.net/bug.php?id=35388 ------------------------------------------------------------------------ [2005-11-28 14:40:02] marcing at smlw dot pl These were 3 machines. ------------------------------------------------------------------------ [2005-11-28 14:32:07] marcing at smlw dot pl Win: php 5.0.3 + mysql 4.1.7 - ok php 5.0.3 + mysql 5.0.16 - crash php 5.0.5 + mysql 5.0.15 - crash php 5.1 + mysql 5.0.16 - crash php 5.1.2-dev + mysql 5.0.16 - crash php 5.1.2-dev + mysql 4.1.15 - ok Linux: php 5.0.5 + mysql 4.1.13 - ok Thats all I can tell u for now. ------------------------------------------------------------------------ [2005-11-28 13:24:05] [EMAIL PROTECTED] 1) Try to downgrade MySQL on Windows and see if it changes anything. 2) Try to upgrade MySQL on Linux and see if it changes anything. This is so obvious, isn't it? ------------------------------------------------------------------------ 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/35428 -- Edit this bug report at http://bugs.php.net/?id=35428&edit=1
