#35428 [Opn->Fbk]: crash when using mysqli with MySQL 5.0.16
| From: | tony2001@php.net | Date: | Mon, 28 Nov 2005 15:11:52 +0000 |
| Subject: | #35428 [Opn->Fbk]: crash when using mysqli with MySQL 5.0.16 | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-89243@lists.php.net to get a copy of this message | ||
ID: 35428
Updated by: tony2001@php.net
Reported By: marcing at smlw dot pl
-Status: Open
+Status: Feedback
Bug Type: MySQLi related
Operating System: WinXP SP2
PHP Version: 5CVS-2005-11-28 (snap)
New Comment:
If you'd install the latest CVS snapshot and the debug symbols, you'd
propably get a bit better backtrace:
http://snaps.php.net/
(c) Jani
Previous Comments:
------------------------------------------------------------------------
[2005-11-28 15:27:02] marcing at smlw dot pl
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 ?? ()
------------------------------------------------------------------------
[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.
------------------------------------------------------------------------
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