Bug #15834 Updated: segmentation fault starting apache with pfpro

From: Date: Sat, 02 Mar 2002 16:43:02 +0000
Subject: Bug #15834 Updated: segmentation fault starting apache with pfpro
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-1484@lists.php.net to get a copy of this message
ID: 15834 Updated by: john.naughton@ipayx.com Reported By: john.naughton@ipayx.com Status: Feedback Bug Type: Reproducible crash Operating System: linux RH7.1 PHP Version: 4.1.2 New Comment: Here it is. #0 0x400d528c in __umoddi3 () from /usr/local/verisign/payflowpro/linux/lib/libpfpro.so No symbol table info available. #1 0x400b7678 in PNVersion () from /usr/local/verisign/payflowpro/linux/lib/libpfpro.so No symbol table info available. Cannot access memory at address 0x3 Previous Comments: ------------------------------------------------------------------------ [2002-03-02 11:38:26] derick@php.net Oops :) Can you hit 'bt full' on the prompt after the crash and post the results again? regards, derick ------------------------------------------------------------------------ [2002-03-02 11:36:56] john.naughton@ipayx.com Following is the message. Thanks. Program received signal SIGSEGV, Segmentation fault. 0x400d528c in __umoddi3 () from /usr/local/verisign/payflowpro/linux/lib/libpfpro.so ------------------------------------------------------------------------ [2002-03-02 11:27:02] derick@php.net gdb /path/to/httpd and enter on the prompt: run -X ------------------------------------------------------------------------ [2002-03-02 11:25:26] john.naughton@ipayx.com Not sure how this could be generated since apache will not start. Follwing is the message that I received when trying to start apache. line 184: 3736 Segmentation fault $HTTPD /usr/local/apache/bin/apachectl start: httpd could not be started ------------------------------------------------------------------------ [2002-03-02 11:19:15] derick@php.net To properly diagnose this bug, we need a backtrace to see what is happening behind the scenes. To find out how to generate a backtrace, please read http://bugs.php.net/bugs-generating-backtrace.php Once you have generated a backtrace, please submit it to this bug report and change the status back to "Open". ------------------------------------------------------------------------ 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/15834 -- Edit this bug report at http://bugs.php.net/?id=15834&edit=1

« previous php.bugs (#1484) next »