On Fri, 10 Aug 2012, Michael Ludwig wrote:
No stack trace. Here's the full output on STDOUT:
[snip]
And then on SDTERR:
Aborted
The script runs to completion before "Aborted" happens.
That does look suspicious.
$ python -v generator.py
…
# cleanup sys
# cleanup __builtin__
# cleanup ints: 24 unfreed ints
# cleanup floats
Aborted
I don't know Python well.
Maybe due to some libraries being loaded in wrong versions?
The script is just using normal Python libraries (including "xml.sax").
The present build of LibXML2 isn't involved at all. This seems like a
Python bug.
If I invoke the script on Linux, running the interpreter through Valgrind,
I see what appear to be numerous double-frees and other memory-handling
errors. I don't know if this is out of the ordinary for the standard
Python interpreter, however.
At any rate, I can fix the tarball so that this script doesn't need to be
invoked in the course of a normal build.
--Daniel
--
Daniel Richard G. || [email protected] || Software Developer
Teragram Linguistic Technologies (a division of SAS)
http://www.teragram.com/
_______________________________________________
xml mailing list, project page http://xmlsoft.org/
[email protected]
https://mail.gnome.org/mailman/listinfo/xml
