After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 64298 - xsltproc segfaults when applied to http://www.w3.org
xsltproc segfaults when applied to http://www.w3.org
Status: VERIFIED FIXED
Product: libxslt
Classification: Platform
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Daniel Veillard
Daniel Veillard
Depends on:
Blocks:
 
 
Reported: 2001-11-11 16:56 UTC by T. V. Raman
Modified: 2009-08-15 18:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description T. V. Raman 2001-11-11 16:56:50 UTC 
xsltproc 1.06-1 --installed from RPM Name        : libxslt                      Relocations: (not relocateable) Version     : 1.0.6                             Vendor: (none) Release     : 1                             Build Date: Tue 30 Oct 2001 06:42:09 AM PST segfaults if you apply a vanila identity.xsl to http://www.w3.org with the --html option.  The page validates correctly using xmllint.  The identity.xsl in question also works with that page when tried on saxon.
Comment 1 Daniel Veillard 2001-11-11 20:39:27 UTC 
  The --html option does not mean that it expect
to parse XHTML or HTML well formed input with an
XML parser but to generate the input tree with
an HTML parser. This of course tend to break
things when the input is actually well formed
XHTML. Applying the identity without the --html
option seems to work.

  However this is rightly a bug and should not segfault,
I commited a fix in CVS:

http://cvs.gnome.org/bonsai/cvsquery.cgi?module=libxslt&branch=HEAD&branchtype=match&dir=libxslt&file=&filetype=match&who=veillard&whotype=match&sortby=Date&hours=&date=explicit&mindate=11%2F11%2F01+15%3A17&maxdate=11%2F11%2F01+15%3A19&cvsroot=%2Fcvs%2Fgnome

  thanks a lot for the report,

Daniel
Comment 2 Daniel Veillard 2001-11-11 20:40:15 UTC 
Oops forgot to toggle the bug to FIXEd state,

Daniel
Comment 3 Daniel Veillard 2001-11-26 14:01:06 UTC 
Should be fixed in the last 2.4.11 release,

 thanks,

Daniel