[xml] Change from 1.8.2 to 1.8.7 causes major failure

Date view Thread view Subject view Author view

From: Byron Ellacott (bje@apnic.net)
Date: Wed Apr 05 2000 - 00:24:16 EDT

I recently updated my libxml from 1.8.2 to 1.8.7; this immediately broke
the application I am writing.

The application reads a number of XML files, converting them to an
internal tree structure. I do this by glob()ing over the files and
reading each in turn.

Now, the first problem is the files have some header details. This means
I can't use xmlParseFile()[0]. So I skip the header, and read the
remainder of the file into a memory buffer, and call xmlParseMemory().
This used to work. Now, it only works for the first file, and fails for
the second and subsequent files. It's not an error in the files, since
removing or renaming the first file causes the second to be read and
parsed, and the third and subsequent to fail.

Now, to top it all off, I cannot find any way short of debugging through
xmlParseMemory to find out what is causing the parse to fail. There are
no error messages printed, which is probably a good thing, but there is no
way (that I could find) to discover what went wrong[1].

Does anyone know why this would happen, if there's a way to find errors
that I've just missed, or what I can do short of installing an older
version? 

--
bje

[0] Why isn't there an xmlParseStream(FILE *input) method?  I'm sure I'm
not the only one who would find it useful.
[1] xmlParseMemory(buffer, buffer_size, &error_code) perhaps.

----
Message from the list xml@xmlsoft.org
Archived at : http://xmlsoft.org/messages/
to unsubscribe: echo "unsubscribe xml" | mail  majordomo@xmlsoft.org

Date view Thread view Subject view Author view

This archive was generated by hypermail 2b29 : Wed Aug 02 2000 - 12:30:09 EDT