Re: [xslt] Segmentation fault with an infinite loop

["William M. Brack" <wbrack mmm com hk>]

Mike Hommey said:
>
> Woops, yes rename toto.xml to menu.xml before launching all.
>
> I still have the crash with latest versions :
>
> mh vaio:/tmp$ xsltproc --version
> Using libxml 20611, libxslt 10108 and libexslt 806
> xsltproc was compiled against libxml 20611, libxslt 10108 and
> libexslt 806
> libxslt 10108 was compiled against libxml 20611
> libexslt 806 was compiled against libxml 20611
> mh vaio:/tmp$ xsltproc html.xsl menu.xml
> Segmentation fault
>
> But interestingly, it works through valgrind:
>
> mh vaio:/tmp$ valgrind xsltproc html.xsl menu.xml
> ==7087== Memcheck, a memory error detector for x86-linux.
> ==7087== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward.
> ==7087== Using valgrind-2.1.1, a program supervision framework for
> x86-linux.
> ==7087== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward.
> ==7087== For more details, rerun with: -v
> ==7087==
> runtime error: file html.xsl line 7 element variable
> xsltApplyOneTemplate: loop found ???
> try increasing xsltMaxDepth (--maxdepth)

<snip>
>
> I'll recompile libxml2/libxslt with debugging symbols and will get
> back
> with more info.
>
> Mike

I don't want to appear overconfident, but with your above results I
would heartily recommend you try running a low-level memory check
program on your system (or, failing that, try removing / swapping
memory modules).

Bill