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".

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

gdb /path/to/httpd

and enter on the prompt:
run -X

Following is the message. Thanks.

Program received signal SIGSEGV, Segmentation fault.
0x400d528c in __umoddi3 ()
   from /usr/local/verisign/payflowpro/linux/lib/libpfpro.so

Oops :)

Can you hit 'bt full' on the prompt after the crash and post the results again?

regards,
derick

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

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

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

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.

Not PHP bug -> Bogus. (Report this to the pfpro people)