Re: [xml] Core dump in DTD validate code in libxml2 2.4.25

On Wed, Oct 09, 2002 at 02:10:58AM -0400, Joe Marcus Clarke wrote:
After upgrading the FreeBSD port of libxml2 to 2.4.25, I noticed a seg
fault everytime the DTD validation code is run.  This was first noticed
in scrollkeeper-0.3.11, but is also visible in xmllint.  The following
command will produce the core dump:

xmllint --dtdvalid

The backtrace is:

#0  0x280ae39b in nodeVPop (ctxt=0xbfbfe910) at valid.c:166
166   PUSH_AND_POP(static, xmlNodePtr, node)
(gdb) bt
#0  0x280ae39b in nodeVPop (ctxt=0xbfbfe910) at valid.c:166
#1  0x280b3fb3 in xmlValidateElementContent (ctxt=0xbfbfe910,
    elemDecl=0x8074c80, warn=1, parent=0x8062140) at valid.c:4629

  Hum, I could not reproduce the problem with gdb ... but caught it with
valgrind, it was of course an uninitialized memory block usage :-(
The DTD validation code has been completely revamped in 2.4.25, but so
far it's the only bug reported, damn that's serious ...
  Please apply the commited patch part for valid.c (enclosed and
in CVS)

  thanks for the report,


Daniel Veillard      | Red Hat Network
veillard redhat com  | libxml GNOME XML XSLT toolkit | Rpmfind RPM search engine

Attachment: valid.patch
Description: Text document

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]