#23942 [Opn->Fbk]: php 4.3.x causes apache2+mod_ssl to sigsev on client authentication

ID: 23942 Updated by: sniper@php.net Reported By: alextxm at tin dot it -Status: Open +Status: Feedback Bug Type: Apache2 related Operating System: Linux PHP Version: 4.3.2 New Comment: 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.. Previous Comments: ------------------------------------------------------------------------ [2003-06-11 05:44:09] alextxm at tin dot it is there anyone interested in this? ------------------------------------------------------------------------ [2003-06-09 08:26:03] alextxm at tin dot it I did some more tests but i'm still unable to obtain a backtrace. I tried : gdb /usr/sbin/apache2 gdb> run -X -D SSL -D PHP output is: Starting program: /usr/sbin/apache2 -X -D PHP -D SSL (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 1024 (LWP 24998)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... ---Type <return> to continue, or q <return> to quit--- is there something i forgot? can you please help me obtaining the bt? I think it would be really helpful having something to work on for this bug. I'm available for any kind of operation aimed to obtain the bt or anything else you would need for inevstigating this bug alessandro ------------------------------------------------------------------------ [2003-06-02 14:33:28] alextxm at tin dot it i'm having problems trying to obtain the bt: i get a lot of "(no debugging symbols found)...(no debugging symbols found)..." messages and when it works (it usually gives me an "Unable to contact site sitename" error in the browser), i get no bt all (even if I ask for a bt) but a message like: LWP thread 26404 ended with error 1 any idea? btw please note that i'm now going to move the whole thing on a new server (where i can try to obtain bt and all what you could need) since the current one is a production one and so I can't shut down it for tests for a long time... ------------------------------------------------------------------------ [2003-06-02 13:21:38] sniper@php.net 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 ------------------------------------------------------------------------ [2003-06-02 13:00:59] alextxm at tin dot it I did some more tests: - enabling your suggested configure cleanups didn't help (=the problem is still there)...thanks anyway (i was using them since previous 4.2.x release) - tested the same setup with apache 1.3.27+mod_ssl : it works fine with php both enabled and disabled... so it seems to be only confined to apache2+ssl+php - MPM used for apache2 is "prefork" ... should I change it? - php 4.3.1 and 4.3.2 both show the issue i'm going to try to obtain a backtrace using httpd -X with php in debug mode. btw, will this work (=will it produce a backtrace) even if the site is not using any php script at all ? ------------------------------------------------------------------------ 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