ID: 45066
Comment by: apex at xepa dot nl
Reported By: dirk at bean-it dot nl
Status: Open
Bug Type: MySQL related
Operating System: Debian 4.0 / x86_64
PHP Version: 5.2.6
New Comment:
Seems this bug is related to /usr/lib/libmysqlclient_r.so.15. Was using
5.0.32, which I upgraded to 5.0.51 and now mysql and mysqli can run
together again.
--
Michiel Brandenburg
Previous Comments:
------------------------------------------------------------------------
[2008-07-22 14:11:10] dirk at bean-it dot nl
mysqlnd is yet to be released for production use... So for now, that
seems not to be the way.
I'll upgrade the mysql libs on a test machine after my vacation (after
august 5th, that is). I'll post my findings here.
Thanks for looking in to this!
Cheers,
Dirk
------------------------------------------------------------------------
[2008-07-21 18:16:20] [EMAIL PROTECTED]
Which means that one will be better served with mysqlnd?
------------------------------------------------------------------------
[2008-07-17 23:09:21] [EMAIL PROTECTED]
By the looks of the valgrind output, IMO, this is some bug in the mysql
lib. Try google for __lll_mutex_lock_wait and you get plenty of hits
pointing to discussion forums. Corrupted heap, -lpthread vs -pthread,
etc. among the possible problems..
------------------------------------------------------------------------
[2008-07-17 08:55:48] dirk at bean-it dot nl
Yes, and I was wrong... :)
In my opinion, bug#42625 went the wrong way (specially the last few
comments), so it would be clearer to start a new bugreport...
------------------------------------------------------------------------
[2008-07-17 08:50:57] [EMAIL PROTECTED]
Ooops, it was you :)
------------------------------------------------------------------------
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/45066
--
Edit this bug report at http://bugs.php.net/?id=45066&edit=1
