Bug #18032 Updated: Configurescript problems, my result in Segfault

ID: 18032 Updated by: sniper@php.net Reported By: vhoel99@grm.hia.no -Status: Open +Status: Feedback Bug Type: Reproducible crash Operating System: Linux 2.4.17 PHP Version: 4.2.1 New Comment: The first configure line of yours (in your initial report) works? But it segfaults when starting apache? You could try this: # cd /usr/src/apache_1.3.xx # make clean # LIBS=-lpthread ./config.status # make # make install And then make sure your httpd is linked with pthread: ldd /usr/local/apache/bin/httpd The list should contain libpthread Previous Comments: ------------------------------------------------------------------------ [2002-06-28 13:47:03] vhoel99@grm.hia.no First of all, I am not that familiar with Core-dumps, GDB and Backtracing. So if I have done anything wrong; I am sorry, but please tell me what to do. I did recompile Apache with "--without-execstrip", and PHP with "--enable-debug". Then I compiled with both gd (2.0.1) and pgsql (7.2), started gdb (gdb ./httpd) and the rest you see under: <cut> GNU gdb 5.0 Copyright 2000 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-slackware-linux"... (gdb) run Starting program: /usr/local/apache/bin/./httpd warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. Program received signal SIGSEGV, Segmentation fault. 0x401166d4 in strcmp () from /lib/libc.so.6 (gdb) bt #0 0x401166d4 in strcmp () from /lib/libc.so.6 #1 0x4042213d in ?? () Cannot access memory at address 0x1 <cut> Now to the zlib and mysql issue. Here is my config: ./configure --prefix=/usr/local \ --with-apxs=/usr/local/apache/bin/apxs \ --enable-exif \ --enable-track-vars \ --enable-magic-quotes \ --enable-ftp \ --with-openssl="/usr/local" \ --with-mysql=/usr/local \ --with-pgsql \ --enable-debug You mean this should fail, because I try to use mysql, but does not specify to use Zlib, nor where zlib is located. Here is (a part of) the output: <cut> Configuring extensions checking if the location of ZLIB install directory is defined... no checking for ZLIB support... no <cut> checking for MySQL support... yes checking for specified location of the MySQL UNIX socket... no checking for MySQL UNIX socket location... /tmp/mysql.sock <cut> checking for mysql_close in -lmysqlclient... yes <cut> As you can see, the configure script does not agree with you on the Zlib/MySQL issue :) I hope this was helpful. If not, just tell me what to do. ------------------------------------------------------------------------ [2002-06-28 11:28:07] sander@php.net Can you generate a backtrace of the crash that happens when you compile with pgsql and gd so we can see what's going on? What versions of pgsql and gd are you using? Also, mysql (apparently) needs zlib, and therefore it's completely logical that configure complains about mysql & zlib when it can't find zlib. ------------------------------------------------------------------------ [2002-06-28 10:44:26] vhoel99@grm.hia.no The system is a standard Slackware 7.1 with an self-compiled Apache. As far as I know, this bug(s) came into PHP version 4.2.0, and are still in the snapshot dated 200206280600. ------------------------------------------------------------------------ [2002-06-28 10:43:52] vhoel99@grm.hia.no The system is a standard Slackware 7.1 with an self-compiled Apache. As far as I know, this bug came into PHP version 4.2.0, and are still in the snapshot dated 200206280600. ------------------------------------------------------------------------ [2002-06-27 20:00:19] sniper@php.net Please try this snapshot: http://snaps.php.net/php4-latest.tar.gz ------------------------------------------------------------------------ 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/18032 -- Edit this bug report at http://bugs.php.net/?id=18032&edit=1