#38882 [Bgs->Opn]: ldap_connect causes Segmentation fault

ID: 38882 User updated by: d dot wynne at ljmu dot ac dot uk Reported By: d dot wynne at ljmu dot ac dot uk -Status: Bogus +Status: Open Bug Type: LDAP related Operating System: SuSE 10.1 x86_64 PHP Version: 4.4.4 New Comment: Now I've implicitly rebuilt php-4.4.4 --without-mysql. Installed and tested that indeed MySQL connections fail, and they do. Still Segmentation fault on ldap_connect. Previous Comments: ------------------------------------------------------------------------ [2006-09-27 16:16:17] d dot wynne at ljmu dot ac dot uk Right I've now compiled MySQL from source code. I'm using the mysql-5.0.18-src RPM as this matches exacly the binary RPM that comes with SuSE 10.1. Configure MySQL: ./configure --prefix=/usr --without-yassl --enable-thread-safe-client --with-gnu-ld --without-server --with-named-curses-libs=/usr/lib64/curses/libcurses.a --without-yassl I believe is the significant part. Built & installed Checked the libraries & header files are in the right place: ldconfig Re-built php from scratch. Configure as before. Installed & restarted Apache2. Same result. Segmentation fault on ldap_connect. Please help. ------------------------------------------------------------------------ [2006-09-20 09:54:42] d dot wynne at ljmu dot ac dot uk Upgraded all 3 MySQl packages to version 5.0.24a. Re-built php-4.4.4 from scratch by deleting top level directoty and re-extracting tar file. Ran configure as beforw. Built no problem. make install /etc/init.d/apache2 restart Same problem when using ldap_connect: [Wed Sep 20 10:38:25 2006] [notice] child pid 21744 exit signal Segmentation fault (11) I can try and get a backtrace if you think it would help. Never done this before but the instructions seem straightforward. ------------------------------------------------------------------------ [2006-09-19 15:57:18] tony2001@php.net >Seems a bit strange that all the mysql_* functions work > OK, and only when you do an ldap_connect the problem with >mysql 5.0.x arises. There is no problem as long as no OpenSSL functions are used. YaSSL and OpenSSL have conflicting names inside, so what you see is just a clash between them. >Would this be worth trying or is there a newer version > which has a better chance. Yes, I think it would. ------------------------------------------------------------------------ [2006-09-19 15:44:40] d dot wynne at ljmu dot ac dot uk Seems a bit strange that all the mysql_* functions work OK, and only when you do an ldap_connect the problem with mysql 5.0.x arises. Anyway the latest version of MySQL 5 seems to be 5.0.24. Would this be worth trying or is there a newer version which has a better chance. Appeciate you help as it seems not to be an issue with PHP, but external libraries. ------------------------------------------------------------------------ [2006-09-19 14:33:21] tony2001@php.net The reason of this problem is YaSSL, which is used in 5.0.x versions of MySQL. AFAIK it has been fixed in latest version, but I'm not 100% sure. Anyway, it's not PHP problem. ------------------------------------------------------------------------ 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/38882 -- Edit this bug report at http://bugs.php.net/?id=38882&edit=1