On Sat, Feb 05, 2005 at 03:15:14PM +0100, Guus Sliepen <email address hidden> wrote:
> On Sat, Feb 05, 2005 at 02:37:36PM +0100, Mike Hommey wrote:
>
> > Mmmmmm it *could* be due to the new libxml2 upload. An upload of libxslt
> > (and therefore xsltproc) is programmed soon and might solve the problem
> > if it is that.
> >
> > I'd be interested in getting a backtrace, though, if you could provide
> > one.
>
> Unfortunately it doesn't fail on x86, so I cannot dig into it myself.
I just tried here. With xsltproc&libxslt1 1.1.8-5 and libxml2 2.6.16-2,
it segfaults. With xsltproc&libxslt1 1.1.12-3 from experimental and
libxml2 2.6.16-2, it doesn't. On x86. So I guess this is it.
On Sat, Feb 05, 2005 at 03:15:14PM +0100, Guus Sliepen <email address hidden> wrote:
> On Sat, Feb 05, 2005 at 02:37:36PM +0100, Mike Hommey wrote:
>
> > Mmmmmm it *could* be due to the new libxml2 upload. An upload of libxslt
> > (and therefore xsltproc) is programmed soon and might solve the problem
> > if it is that.
> >
> > I'd be interested in getting a backtrace, though, if you could provide
> > one.
>
> Unfortunately it doesn't fail on x86, so I cannot dig into it myself.
I just tried here. With xsltproc&libxslt1 1.1.8-5 and libxml2 2.6.16-2,
it segfaults. With xsltproc&libxslt1 1.1.12-3 from experimental and
libxml2 2.6.16-2, it doesn't. On x86. So I guess this is it.
Mike