On Wed, Sep 29, 2004 at 02:22:31PM -0400, Alan Cox wrote:
On Wed, Sep 29, 2004 at 02:18:04PM -0400, seth vidal wrote:
> I have, It is a set of tests I run on the metadata import, just to see
> how it errors out. In every case I've seen it falls over with a raised
> exception complaining about a broken file.
>
> what happens when you run xmllint on the same file?
I don't have the one that blew it up any more. From the error the file
appeared to have been truncated
The XML file parsing is done with the xmlReader, it should operate
on constant memory whether the instance is well-formed or not, I have
never seen such a memory explosion behaviour from the parser itself,
or at least it was never reported. Maybe this is related to the way the
exception is handled at the Python level (libxml2-2.6.14 just released
slightly refactor libxml2 python exceptions classes but this looked safe
to me, and the thread started before I pushed that release so ...)
Daniel
--
Daniel Veillard | Red Hat Desktop team
http://redhat.com/
veillard(a)redhat.com | libxml GNOME XML XSLT toolkit
http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine
http://rpmfind.net/