Hi Toby,
thanks for digging into this so thoroughly and providing useful minimal
examples. I can confirm segfaults of 568382a.pl without the 'push @keep'
with the latest libxml-libxslt-perl (1.71-1). As I'm not terribly
experienced with either XML/XSLT or XS, I've forwarded the issue
upstream
reassign 568382 libxml-libxslt-perl
thanks
I'm now becoming convinced that this is a memory management issue
between Perl and libxslt - I think that both are trying to free the
same objects. So I'm reassigning this - feel free to punt it back to
libxslt if appropriate.
The following code should
Package: libxslt1.1
Version: 1.1.26-1+b1
Severity: normal
Here's my stylesheet (machine-generated, as you can probably tell):
/
| ?xml version=1.0?
| x:stylesheet xmlns:exsl=http://exslt.org/common;
xmlns:osmt=http://geotagman.sourceforge.net/;
This seems to occur only when I use my registered extension functions in
two different modes; I'll try to narrow it down further.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Okay, I think I've got a minimal repro (appended). It's possible the
fault lies in the Perl interface, in which case this should be
reassigned to the `libxml-libxslt-perl' package.
The bug only seems to be triggered if we pass nodes from exsl:node-set()
into an unrelated extension function;
5 matches
Mail list logo
