Is anyone else using php4-xslt on OpenBSD 3.7? After upgrading from 3.6
(including upgrading all ports) I'm seeing reproducible segmentation
faults whenever the xslt extension is called.

Even code as simple as:

test.php:
<?php
    $xh = xslt_create();
?>

causes Apache to segfault. Everything was working fine in 3.6. I'd still
like to find a solution before giving up and submitting a bug, but I'm
stumped. Here's the backtrace (with symbols):

Starting program: /usr/sbin/httpd -u -X

(request test.php)

Program received signal SIGSEGV, Segmentation fault.
0x0a4f7148 in ?? ()
(gdb) bt
#0  0x0a4f7148 in ?? ()
#1  0x0b86a6ad in operator new(unsigned) (sz=116) at
/usr/src/gnu/lib/libstdc++/libstdc++/libsupc++/new_op.cc:42
#2  0x0b6a7838 in SablotCreateSituation (sPtr=0xcfbf9570) at
sablot.cpp:118
#3  0x0675b3c4 in zif_xslt_create (ht=0, return_value=0x3c15ac2c,
this_ptr=0x0, return_value_used=1)
    at
/usr/ports/www/php4/extensions/w-php-4.3.11-no_bz2-no_curl-no_dba-no_dba
se-no_dbx-no_filepro-no_gmp-no_imap-no_ldap-no_mcrypt-no_mhash-no_ncurse
s-no_odbc-no_pdf-no_pgsql-no_shmop-no_snmp-no_sybase_ct/php-4.3.11/ext/x
slt/sablot.c:226
#4  0x0fb0126a in execute (op_array=0x3c15df0c) at
/usr/ports/www/php4/core/w-php4-core-4.3.11/php-4.3.11/Zend/zend_execute
.c:1654
#5  0x0faf2deb in zend_execute_scripts (type=8, retval=0x0,
file_count=3) at
/usr/ports/www/php4/core/w-php4-core-4.3.11/php-4.3.11/Zend/zend.c:926
#6  0x0faca106 in php_execute_script (primary_file=0xcfbfae30) at
/usr/ports/www/php4/core/w-php4-core-4.3.11/php-4.3.11/main/main.c:1745
#7  0x0fb05072 in apache_php_module_main (r=0x3c132034,
display_source_mode=0) at
/usr/ports/www/php4/core/w-php4-core-4.3.11/php-4.3.11/sapi/apache/sapi_
apache.c:54
#8  0x0fb05a76 in send_php (r=0x3c132034, display_source_mode=0,
filename=0x0) at
/usr/ports/www/php4/core/w-php4-core-4.3.11/php-4.3.11/sapi/apache/mod_p
hp4.c:621
#9  0x0fb05c0a in send_parsed_php (r=0x3c132034) at
/usr/ports/www/php4/core/w-php4-core-4.3.11/php-4.3.11/sapi/apache/mod_p
hp4.c:636
#10 0x1c035f72 in ap_invoke_handler (r=0x3c132034) at http_config.c:521
#11 0x1c046687 in process_request_internal (r=0x3c132034) at
http_request.c:1188
#12 0x1c046837 in ap_process_request (r=0x3c132034) at
http_request.c:1204
#13 0x1c03f5fd in child_main (child_num_arg=-809527952) at
http_main.c:2531
#14 0x1c03f7f2 in make_child (s=0x3c040034, slot=0, now=-809527856) at
http_main.c:2602
#15 0x1c03f860 in startup_children (number_to_start=5) at
http_main.c:2657
#16 0x1c040341 in standalone_main (argc=3, argv=0xcfbfb17c) at
http_main.c:2985
#17 0x1c040906 in main (argc=3, argv=0xcfbfb17c) at http_main.c:3274


RBC Dain Rauscher does not accept buy, sell or cancel orders by e-mail, or any 
instructions by e-mail that would require your signature.  Information 
contained in this communication is not considered an official record of your 
account and does not supersede normal trade confirmations or statements.  Any 
information provided has been prepared from sources believed to be reliable but 
is not guaranteed, does not represent all available data necessary for making 
investment decisions and is for informational purposes only.

This e-mail may be privileged and/or confidential, and the sender does not 
waive any related rights and obligations.  Any distribution, use or copying of 
this e-mail or the information it contains by other than an intended recipient 
is unauthorized.  If you receive this e-mail in error, please advise me (by 
return e-mail or otherwise) immediately.

Information received by or sent from this system is subject to review by 
supervisory personnel, is retained and may be produced to regulatory 
authorities or others with a legal right to the information.


Reply via email to