Bug #17931 Updated: Segfault when passing array as second arg to xslt_set_error_handler

From: Date: Thu, 04 Jul 2002 20:54:00 +0000
Subject: Bug #17931 Updated: Segfault when passing array as second arg to xslt_set_error_handler
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-13151@lists.php.net to get a copy of this message
ID: 17931 Updated by: msopacua@idg.nl Reported By: marcel@beerta.de Status: Open Bug Type: XSLT related Operating System: Linux PHP Version: 4.2.1 New Comment: Hi, could you verify if it works with current Sablot CVS version? See: http://www.gingerall.cz/charlie/ga/xml/p_sab.xml for details on anoncvs access. This version works for me, and is actually the same bug as #17791. Previous Comments: ------------------------------------------------------------------------ [2002-06-24 04:28:31] sniper@php.net reclassified ------------------------------------------------------------------------ [2002-06-23 05:49:04] boris@mediatis.de Same on PHP 4.1.1, 4.2.1, 4.3.0-dev all tested with sablot 0.90 on debian 2.2 ------------------------------------------------------------------------ [2002-06-23 05:36:25] marcel@beerta.de I get a segfault if i want to pass an array with $object,'method' as second arg to xslt_set_error_handler. the line looks like this: xslt_set_error_handler($this->_parser, array($this,'xslt_trap_error') ); Backtrace: #0 0x401f594a in __morecore () from /lib/libc.so.6 #1 0x401f5950 in __morecore () from /lib/libc.so.6 #2 0x40452b22 in Situation::message () from /usr/lib/libsablot.so.0 #3 0x404487da in Processor::report () from /usr/lib/libsablot.so.0 #4 0x4044749c in Processor::setHandler () from /usr/lib/libsablot.so.0 #5 0x4044cb6c in SablotUnregHandler () from /usr/lib/libsablot.so.0 #6 0x403870b0 in free_processor (rsrc=Cannot access memory at address 0x21 ) at sablot.c:617 Cannot access memory at address 0x1 ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=17931&edit=1

« previous php.bugs (#13151) next »