[lxml-dev] Tracking down bugs
Filip Salomonsson
filip.salomonsson at gmail.com
Thu Dec 4 15:00:16 CET 2008
lxml occasionally goes crashing on me, with an error message and
backtrace like the one below. Usually, the same program runs just fine
if I try again. What can I do to track down the cause?
*** glibc detected *** python: free(): invalid pointer: 0x0a0388cb ***
======= Backtrace: =========
/lib/libc.so.6[0x1d3b16]
/lib/libc.so.6(cfree+0x90)[0x1d7070]
/usr/lib/libxml2.so.2(xmlNodeSetName+0xa5)[0x68fc0c5]
/home/stp02/salo/lib/python/lxml-2.1.2-py2.4-linux-i686.egg/lxml/etree.so[0x3b988f]
/usr/lib/libpython2.4.so.1.0[0x5437d83]
/usr/lib/libpython2.4.so.1.0(PyObject_GenericSetAttr+0x104)[0x5455b84]
/usr/lib/libpython2.4.so.1.0(PyObject_SetAttr+0xbb)[0x54561db]
/usr/lib/libpython2.4.so.1.0(PyEval_EvalFrame+0x2d51)[0x548cd91]
/usr/lib/libpython2.4.so.1.0(PyEval_EvalCodeEx+0x896)[0x548fc76]
/usr/lib/libpython2.4.so.1.0(PyEval_EvalCode+0x63)[0x548fd03]
/usr/lib/libpython2.4.so.1.0[0x54acad8]
/usr/lib/libpython2.4.so.1.0(PyRun_SimpleFileExFlags+0x198)[0x54ae1e8]
/usr/lib/libpython2.4.so.1.0(PyRun_AnyFileExFlags+0x7a)[0x54ae8ca]
/usr/lib/libpython2.4.so.1.0(Py_Main+0xb85)[0x54b52d5]
python(main+0x32)[0x80485b2]
/lib/libc.so.6(__libc_start_main+0xdc)[0x180dec]
python[0x80484c1]
--
filip salomonsson
More information about the lxml-dev
mailing list