On Thu, 2005-03-03 at 21:34 -0800, Steve Langasek wrote:

> I think Adam sent this follow-up to the wrong address:

No, I did receive it, but I've been busy trying to get one of my
applications ready to be sponsored as a new Debian package... anyway
thanks for the subtle nudge, the requested information is below. 

> > Would it be too much trouble to ask you to dist-upgrade to the latest
> > stable, then restart apache?  And if the problem still persists, could you
> > start checking library linkage, etc.  For instance:

Ok, I dist-upgraded today (Fri 4 Mar 2005 NZDT) and upgraded half my
system it seemed including apache and php4, needless to say the segfault
still exists. Current versions:

xenon:/etc/php4/apache# dpkg -s apache | egrep "Package|Version"
Package: apache
Version: 1.3.33-4

xenon:/etc/php4/apache# dpkg -s php4 | egrep "Package|Version"
Package: php4
Version: 4:4.3.10-8

xenon:/etc/php4/apache# dpkg -s php4-imap | egrep "Package|Version"
Package: php4-imap
Version: 4:4.3.10-8

xenon:/etc/php4/apache# dpkg -s php4-pgsql | egrep "Package|Version"
Package: php4-pgsql
Version: 3:4.3.10-2

OK. Tracing libraries

> > ldd /usr/lib/php4/20020429-zts/imap.so

xenon:/etc/php4/apache# ldd /usr/lib/php4/20020429-zts/imap.so
        libssl.so.0.9.7 => /usr/lib/i686/cmov/libssl.so.0.9.7 (0x40020000)
        libc-client.so.2002edebian => /usr/lib/libc-client.so.2002edebian 
(0x40051000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x4010e000)
        libpam.so.0 => /lib/libpam.so.0 (0x4013b000)
        libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x40143000)
        libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x40158000)
        libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x401c0000)
        libcom_err.so.2 => /lib/libcom_err.so.2 (0x401e2000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x401e6000)
        libc.so.6 => /lib/libc.so.6 (0x40237000)
        libcrypto.so.0.9.7 => /usr/lib/i686/cmov/libcrypto.so.0.9.7 
(0x4036a000)        libdl.so.2 => /lib/libdl.so.2 (0x40469000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x4046c000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)

(as an aside there is also a /usr/lib/php4/20020429/ directory... I'm
not sure if this is important or not... I'm ignoring it for now)

> > (make sure those are all pointing at stuff provided by Debian packages)

xenon:/etc/php4/apache# ldd /usr/lib/php4/20020429-zts/imap.so | cut -f2 -d'>' 
| cut -f2 -d' ' | xargs -n1 dpkg -S
libssl0.9.7: /usr/lib/i686/cmov/libssl.so.0.9.7
libc-client2002edebian: /usr/lib/libc-client.so.2002edebian
libc6: /lib/libcrypt.so.1
libpam0g: /lib/libpam.so.0
libkrb53: /usr/lib/libgssapi_krb5.so.2
libkrb53: /usr/lib/libkrb5.so.3
libkrb53: /usr/lib/libk5crypto.so.3
libcomerr2: /lib/libcom_err.so.2
libc6: /lib/libpthread.so.0
libc6: /lib/libc.so.6
libssl0.9.7: /usr/lib/i686/cmov/libcrypto.so.0.9.7
libc6: /lib/libdl.so.2
libc6: /lib/libresolv.so.2
libc6: /lib/ld-linux.so.2

> > (check md5sums of all the libraries pointed to by ldd, and forward those
> > to the bug)

cbac8192e29696f574bc84510a5e50d3  /usr/lib/i686/cmov/libssl.so.0.9.7
2e003f04d63a76a7c0b47c93f9978346  /usr/lib/libc-client.so.2002edebian
c6cc3a979bc126e03f33c812ad504072  /lib/libcrypt.so.1
94a83647fed97341ccbbbf70264a9b8b  /lib/libpam.so.0
056175c4b810cbd72579e281ba484c89  /usr/lib/libgssapi_krb5.so.2
3ee58509a3418474cf637a9e771d6f85  /usr/lib/libkrb5.so.3
adae129ee24f5dc1fba55dcb6d20a1cc  /usr/lib/libk5crypto.so.3
f55b6b1a0204ed0da5de09834ada2dfd  /lib/libcom_err.so.2
2653824cdc505d11928c6096ff97d653  /lib/libpthread.so.0
bce84e3c89fd5c5e708de2dda550b3a1  /lib/libc.so.6
50eaf9bda72f79b1ff9d7ee7dcae2607  /usr/lib/i686/cmov/libcrypto.so.0.9.7
cddad62deb247c4ab49cdd0e21c4725d  /lib/libdl.so.2
4ec1ad984131583a5c68baae010895a6  /lib/libresolv.so.2
96fa3b4f2f0ba749a09d5621af2f7d62  /lib/ld-linux.so.2


> > (dpkg -S each of those libraries and forward the versions of the packages
> > owning them)

xenon:/etc/php4/apache# ldd /usr/lib/php4/20020429-zts/imap.so | cut -f2 -d'>' 
| cut -f2 -d' ' | xargs -n1 dpkg -S | cut -f1 -d':' | xargs -n1 dpkg -s | egrep 
"Package|Version"
Package: libssl0.9.7
Version: 0.9.7e-2
Package: libc-client2002edebian
Version: 7:2002edebian1-6
Package: libc6
Version: 2.3.2.ds1-20
Package: libpam0g
Version: 0.76-22
Package: libkrb53
Version: 1.3.6-1
Package: libkrb53
Version: 1.3.6-1
Package: libkrb53
Version: 1.3.6-1
Package: libcomerr2
Version: 1.35-6
Package: libc6
Version: 2.3.2.ds1-20
Package: libc6
Version: 2.3.2.ds1-20
Package: libssl0.9.7
Version: 0.9.7e-2
Package: libc6
Version: 2.3.2.ds1-20
Package: libc6
Version: 2.3.2.ds1-20
Package: libc6
Version: 2.3.2.ds1-20

> > Also, a copy of your php.ini (stripped of comments) and your apache
> > configs might prove helpful in me reproducing this.  If you can come up
> > with a really minimal config that still breaks for you, that's even
> > better.

Really minimal configs attached, you basically can't remove anything
else from them, or the segfault goes away. 

- Uncomment mod_ssl and the segfault vanishes
- Comment either of the modules in php.in and the segfault vanishes
- Remove virtual host and the segfault vanishes
- Remove config_log_module or dir_module and the segfault vanishes

It's been great fun (although time consuming!) tracking all this down,
so I hope it helps to solve the bug!

-- 
Matt Brown
[EMAIL PROTECTED]
Mob +64 275 611 544 www.mattb.net.nz
ServerType standalone
ServerRoot /etc/apache
LockFile /var/lock/apache.lock
PidFile /var/run/apache.pid
ScoreBoardFile /var/run/apache.scoreboard

LoadModule config_log_module /usr/lib/apache/1.3/mod_log_config.so
LoadModule dir_module /usr/lib/apache/1.3/mod_dir.so
LoadModule php4_module /usr/lib/apache/1.3/libphp4.so
#LoadModule ssl_module /usr/lib/apache/1.3/mod_ssl.so

NameVirtualHost *
<VirtualHost *>
        ServerAdmin [EMAIL PROTECTED]
        DocumentRoot /tmp
        ServerName www.example.com
        ErrorLog /tmp/apache-error.log
</VirtualHost>
[PHP]
extension=imap.so
extension=pgsql.so

Reply via email to