php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #15834 segmentation fault starting apache with pfpro
Submitted: 2002-03-02 11:18 UTC Modified: 2002-04-26 22:37 UTC
Votes:2
Avg. Score:5.0 ± 0.0
Reproduced:2 of 2 (100.0%)
Same Version:2 (100.0%)
Same OS:1 (50.0%)
From: john dot naughton at ipayx dot com Assigned:
Status: Not a bug Package: Reproducible crash
PHP Version: 4.1.2 OS: linux RH7.1
Private report: No CVE-ID: None
 [2002-03-02 11:18 UTC] john dot naughton at ipayx dot com
I get a segmentation fault when start apache when php4.1.2 is compiled with verisign payflowpro.  If a recompile with this option everything is OK. I have encountered this problem with all previous versions also.

Patches

Add a Patch

Pull Requests

Add a Pull Request

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2002-03-02 11:19 UTC] 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".
 [2002-03-02 11:25 UTC] john dot naughton at ipayx dot 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:27 UTC] derick@php.net
gdb /path/to/httpd

and enter on the prompt:
run -X
 [2002-03-02 11:36 UTC] john dot naughton at ipayx dot 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:38 UTC] 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:43 UTC] john dot naughton at ipayx dot com
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
 [2002-03-02 22:08 UTC] rasmus@php.net
This can happen when you link a library not compiled/linked with gcc into an app that is, or vice versa.  Try adding this switch to your PHP ./configure line:

--enable-libgcc
 [2002-03-03 08:19 UTC] john dot naughton at ipayx dot com
Same error and message. Following are my configuration parameters - if this helps.  Thanks.

./configure --with-apache=/usr/local/apache_1.3.22.src --prefix=/usr/local  --enable-libgcc --enable-pic --enable-shared --enable-inline-optimization  --with-exec-dir=/usr/local --with-png --with-zlib  --enable-magic-quotes --enable-safe-mode --enable-sockets --enable-sysvsem --enable-sysvshm --enable-track-vars --enable-yp --enable-ftp --enable-wddx --with-mysql  --with-xml --with-mcrypt --with-jpeg --with-tiff --with-pfpro=/usr/local/verisign/payflowpro/linux
 [2002-04-26 17:26 UTC] tjw at webteam dot net
The problem here is clearly Verisign's choice to 
statically link to OpenSSL 0.9.5a.  I've had the same 
problem in the past and was able to get it working 
by loading libphp4.so before libssl.so in httpd.conf. 
 
I currently have php 4.1.2 working with libcurl, and 
mod_ssl using libpfpro.so (L300).   
 
I am not however able to get the same combination to work 
with php 4.2.0 or the latest libpfpro.so (L304).   
 
Again, this is a VeriSign problem, not a PHP problem.  If 
anyone knows how to get in contact with the PayFlowPro 
people, please let them know of this incompatability.
 [2002-04-26 22:37 UTC] sniper@php.net
Not PHP bug -> Bogus. (Report this to the pfpro people)

 
PHP Copyright © 2001-2022 The PHP Group
All rights reserved.
Last updated: Sat Dec 03 23:05:52 2022 UTC