on segfaulting xsltproc

For the record:

I've helped debug someone's segfaulting xsltproc over the
past few weeks, 
and we've found the cause of the segfaults now. The user had
the following 
line in /usr/pkg/share/xml/catalog:

        <nextCatalog
catalog="/usr/pkg/share/xml/catalog" />

With the file loading itself again and again, the resulting
segfault 
(probably due to some stack overflow) is no big surprise.

I'm not sure (yet...) where that line comes from, but if you
see your 
system behave in a similar way, that's where you can start
looking.


  - Hubert

Hubert Feyrer <hubertfeyrer.de> wrote:
> 
> For the record:
> 
> I've helped debug someone's segfaulting xsltproc over
the past few weeks, 
> and we've found the cause of the segfaults now. The
user had the following 
> line in /usr/pkg/share/xml/catalog:
> 
>        <nextCatalog
catalog="/usr/pkg/share/xml/catalog" />
> 
> With the file loading itself again and again, the
resulting segfault 
> (probably due to some stack overflow) is no big
surprise.
> 
> I'm not sure (yet...) where that line comes from, but
if you see your 
> system behave in a similar way, that's where you can
start looking.

I've traced the problem a bit. This is a fault of libxml2
(catalog
processing is its work). You can see a problem report at
http
://bugzilla.gnome.org/show_bug.cgi?id=383687  The report
also
contains test harness to check is you affected. 

Would hope Daniel (or someone from libxml2 team) will fix
that quickly.

--
Mishka.