Re: Bug #14381: xlst_error causes error with valid XSLT processor instance
| From: | Hans Rakers | Date: | Fri, 07 Dec 2001 18:01:42 +0000 |
| Subject: | Re: Bug #14381: xlst_error causes error with valid XSLT processor instance | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-72876@lists.php.net to get a copy of this message | ||
At 09:33 7-12-2001 -0800, Rasmus Lerdorf wrote:
At 09:10 7-12-2001 -0800, Rasmus Lerdorf wrote:I adapted the php source to read "xslt_process($xsl_handle, $xmlData, $xslData);", and this results in another (weird) segfault. Backtrace follows: Program received signal SIGSEGV, Segmentation fault. 0x40081963 in Situation::generateMessage (this=0x6f660909, type=1932358766,AFAIK (and according to the manual) the first argument to xslt_process() should be a string containing the XSL data ($xslData) and not the XSLT processor handle. Please advise. Then the manual is wrong. The code is clearly expecting arguments in this order: resource processor, string xml, string xsl -Rasmusthe following code causes Apache processes to segfault:It obviously shouldn't crash, but the first argument to xslt_process() needs to be $xsl_handle in your case. The warning you are seeing is correct. -Rasmus$xsl_handle = xslt_create(); echo $xsl_handle; // returns a valid xslt processor handle // $xslData and $xmlData contain valid information xslt_process($xslData, $xmlData, $result); echo xslt_error($xsl_handle); xslt_free($xsl_handle);This piece of code also returns a "Warning: Supplied argument is not a valid XSLT Processor resource in *** on line 27", where line 27 is "xslt_process($xslData, $xmlData, $result); "
code=543521385, arg1=@0x7039203a, arg2=@0xa203b74, theMessage=@0x6f660909)
at situa.cpp:263
263 if (messenger && !(flags & SAB_NO_ERROR_REPORTING))
Current language: auto; currently c++
(gdb) bt
#0 0x40081963 in Situation::generateMessage (this=0x6f660909,
type=1932358766, code=543521385, arg1=@0x7039203a, arg2=@0xa203b74,
theMessage=@0x6f660909) at situa.cpp:263
#1 0xa203b30 in ?? () at eval.c:88
Cannot access memory at address 0x30303030
--
Hans Rakers (hans@parse.nl) Tel: +31 (0)23 5325689
System engineer / Webmaster / Webdeveloper Fax: +31 (0)23 5324957
Parse - TeKoop http://www.parse.nl
Haarlem, the Netherlands http://www.tekoop.nl