#14860 [NoF->Asn]: PHP segfault in mysql driver

ID: 14860 Updated by: zak@php.net Reported By: aleigh@tessier.com -Status: No Feedback +Status: Assigned Bug Type: MySQL related Operating System: Solaris 8 PHP Version: 4.1.1 -Assigned To: +Assigned To: zak New Comment: Assigning all open mysql bugs to myself for 4.3 QA cycle. Previous Comments: ------------------------------------------------------------------------ [2002-08-08 01:00:13] php-bugs@lists.php.net No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open". ------------------------------------------------------------------------ [2002-07-07 22:05:24] sniper@php.net This should be fixed in CVS, so please try this snapshot: http://snaps.php.net/php4-latest.tar.gz ------------------------------------------------------------------------ [2002-04-03 14:25:35] ronen@greyzone.com This bug may be related to #16272. Ronen. ------------------------------------------------------------------------ [2002-02-28 14:20:49] ronen@greyzone.com We've had the same exact problem - specifically with mysql_fetch_array(), and with the exact same symptoms. Not predictable, random occurance, etc'. We're running PHP 4.1.1 as a static build for Apache 1.3.22 on RedHat Linux 6.1. MySQL version is 3.23.42 ------------------------------------------------------------------------ [2002-01-12 09:25:24] biancardi@xware.it I'am having the same problem using apache2 and latest cvs. I see that ext/mysql/libmysql/ is always compiled with #define UNDEF_THREADS_HACK so producing a non thread safe mysql builtin library. Not using the builtin libmysql this problem is solved. Don't know if it's the same for win32 builds. I also noticed that build this libmysql the debug code is not turned off definig DBUG_OFF (?), is this intented ? ------------------------------------------------------------------------ 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/14860 -- Edit this bug report at http://bugs.php.net/?id=14860&edit=1