ID: 28286
Updated by: [EMAIL PROTECTED]
Reported By: stuart dot herbert at boxuk dot com
Status: Open
Bug Type: DOM XML related
Operating System: RHES 3.1
PHP Version: 4.3.6
New Comment:
The crash you get is from domxml, not xslt extension (sablotron), so
assumed you were using the libxslt functions. This being the case,
without a reproducing script, debugging domxml is extremely difficult
as you need to figure out where the issue between the engine, domxml
and libxml lies.
Previous Comments:
------------------------------------------------------------------------
[2004-05-17 15:00:36] stuart dot herbert at boxuk dot com
Hiya,
Erm, I'm a bit confused. xslt isn't an object in PHP 4 ;-) It sounds
like you're talking about the xslt functionality that's new in PHP 5
;-)
Our xslt_process call looks like this:
$output = xslt_process($this->processor, 'arg:/_xml', 'arg:/xsl', NULL,
$arguments);
There's no documented parameter to xslt_process() to force a copy.
If I'm going to 'poke about' with gdb, it'd help if you could point me
in the right direction. The core dump isn't very helpful - if I
understand it correctly, it's just saying that the Zend engine is dying
after executing the script because something messed up the internal
linked lists. Some sort of patch that will catch the list corruption
much closer to where it occurs would really help ;-)
Best regards,
Stu
------------------------------------------------------------------------
[2004-05-17 13:36:51] [EMAIL PROTECTED]
What does your xslt_process call look like?
No easy way to debug this without a script, but can you try forcing a
copy on the document (there's an additional parameter that can be
passed to xslt_process to force a doc copy). Not sure what you have for
parameters, but try something like:
xslt->process(doc, NULL, NULL, NULL, 1);
See if it still crashes doing that. If it still does and you dont have
a reproducing script then you will have to sit down with gdb and try to
find where the problem is coming from.
------------------------------------------------------------------------
[2004-05-17 10:10:31] stuart dot herbert at boxuk dot com
Hiya,
Sorry - I've been unable to create a short script to reproduce this
fault yet. Our CMS is a large application which uses DOM extensively.
Trying to find 20 or so lines to re-create the problem is non-trivial.
Can you supply a debugging patch, which will help capture additional
information?
libxml is 2.6.9, and libxslt is 1.1.6.
Best regards,
Stu
------------------------------------------------------------------------
[2004-05-15 01:00:03] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
------------------------------------------------------------------------
[2004-05-07 14:47:56] [EMAIL PROTECTED]
Thank you for this bug report. To properly diagnose the problem, we
need a short but complete example script to be able to reproduce
this bug ourselves.
A proper reproducing script starts with <?php and ends with ?>,
is max. 10-20 lines long and does not require any external
resources such as databases, etc.
If possible, make the script source available online and provide
an URL to it here. Try avoid embedding huge scripts into the report.
Can you also include the libxml and libxslt versions you are using?
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/28286
--
Edit this bug report at http://bugs.php.net/?id=28286&edit=1
