ID: 23942
User updated by: alextxm at tin dot it
Reported By: alextxm at tin dot it
-Status: Feedback
+Status: Open
Bug Type: Apache2 related
Operating System: Linux
PHP Version: 4.3.2
New Comment:
output of ldd libmysqlclient.so for each platform (cfr. my previous
comment) :
rh9)
libz.so.1 => /usr/lib/libz.so.1 (0x40053000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x40061000)
libnsl.so.1 => /lib/libnsl.so.1 (0x4008e000)
libm.so.6 => /lib/tls/libm.so.6 (0x400a4000)
libc.so.6 => /lib/tls/libc.so.6 (0x42000000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
gentoo 1.2)
libz.so.1 => /usr/lib/libz.so.1 (0x40047000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x40055000)
libnsl.so.1 => /lib/libnsl.so.1 (0x40082000)
libm.so.6 => /lib/libm.so.6 (0x40097000)
libssl.so.0.9.7 => /usr/lib/libssl.so.0.9.7 (0x400b8000)
libcrypto.so.0.9.7 => /usr/lib/libcrypto.so.0.9.7 (0x400e6000)
libc.so.6 => /lib/libc.so.6 (0x401d9000)
libdl.so.2 => /lib/libdl.so.2 (0x402fc000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
gentoo 1.4)
libz.so.1 => /usr/lib/libz.so.1 (0x40052000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x40060000)
libnsl.so.1 => /lib/libnsl.so.1 (0x4008d000)
libm.so.6 => /lib/libm.so.6 (0x400a1000)
libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x400c3000)
libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x400f1000)
libc.so.6 => /lib/libc.so.6 (0x401b1000)
libdl.so.2 => /lib/libdl.so.2 (0x402da000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
i'm also investigating more things... let me know if you need to me to
test some specific items
alessandro
Previous Comments:
------------------------------------------------------------------------
[2003-06-14 17:19:25] [EMAIL PROTECTED]
That sounds odd. And as you're not running Apache2 as threaded (worker,
or whatever that MPM was again), it shouldn't be thread-safety issue
either.
Could you check what libmysqlclient.so is linked with
on those systems? Output of:
# ldd libmysqlclient.so
And FYI: the bundled mysql library is far from obsolete.
(it works, doesn't it? :)
------------------------------------------------------------------------
[2003-06-14 15:40:21] alextxm at tin dot it
finally, i've found the problem: compiling php 4.3.2 with
--with-mysql=/path-to-mysql staically linked is the culprit.
The problem can be avoided using --with-mysql and so using PHP's
built-in (but obsolete) mysql interface or using:
--with-mysql=shared,/path-to-mysql and then enabling php_mysql.so in
php.ini
Tests had been accomplished on three machines:
a) gentoo linux 1.2: glibc 2.2.5, php 4.3.2, apache 2.0.45/46, mysql
4.0.12, openssl 0.9.6j
b) gentoo linux 1.4rc4: glibc 2.3.1, php 4.3.2, apache 2.0.46, mysql
4.0.13, openssl 0.9.7b
c) redhat 9: php 4.2.2, apache 2.0.40, openssl 0.9.7a, mysql-4.0.10
alessandro
------------------------------------------------------------------------
[2003-06-14 08:02:41] alextxm at tin dot it
i'm doing some more tests... an interesting thing: on Redhat 9.0 it
works fine (openssl 0.9.7a, php 4.2.2, apache 2.0.40 - both stock
versions) . I'm trying to figure out where the problem is. I'll let you
know, probaly there is something in my setup which causes php or apache
to behave strangely.
alessandro
------------------------------------------------------------------------
[2003-06-11 11:28:03] [EMAIL PROTECTED]
Try reduce the configure options to the bare minimum
first. Then if you don't get any segfaults, try every
excluded option one by one to see which one is causing
this.
And for the backtrace you just need to keep pressing
'enter' until it gets there..the first couple of screens
gdb is loading the symbols from every linked library, you
can ignore it..
------------------------------------------------------------------------
[2003-06-02 13:21:38] [EMAIL PROTECTED]
No, don't change the MPM.
And yes, you will get a backtrace always, it's not really
PHP related thing.
# gdb httpd
(gdb) run -X -DSSL
..then access the page causing the crash..
(gdb) bt
------------------------------------------------------------------------
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/23942
--
Edit this bug report at http://bugs.php.net/?id=23942&edit=1
