[lxml-dev] a different segfault

Roger Patterson rogerpatterson at gmail.com
Thu Jun 5 01:59:45 CEST 2008


Hi Stefan et al.

I am getting a mysterious segfault using the XSLT lib.
Basically, if I have:
    <xsl:strip-space elements="*"/>

in my transform, I get the segfault, if I remove that line, it works fine.

Now, I haven't distilled it down to a succinct example yet, and my 
transform and code are pretty large, but I was wondering if anyone else 
has experienced this?

cheers
-Roger

The dump looks like this:

*** glibc detected *** python: double free or corruption (!prev): 
0x000000000f7dab00 ***
======= Backtrace: =========
/lib64/libc.so.6[0x352d46e890]
/lib64/libc.so.6(cfree+0x8c)[0x352d471fac]
/usr/lib64/libxml2.so.2(xmlFreeNodeList+0x177)[0x3536e4ff27]
/usr/lib64/libxml2.so.2(xmlFreeNodeList+0x89)[0x3536e4fe39]
/usr/lib64/libxml2.so.2(xmlFreeNodeList+0x89)[0x3536e4fe39]
/usr/lib64/libxml2.so.2(xmlFreeDoc+0xb6)[0x3536e4fc96]
/usr/lib/python2.4/site-packages/lxml-2.0.4-py2.4-linux-x86_64.egg/lxml/etree.so[0x2aaaaf1b79c8]
/usr/lib/python2.4/site-packages/lxml-2.0.4-py2.4-linux-x86_64.egg/lxml/etree.so[0x2aaaaf1b900d]
/usr/lib64/libpython2.4.so.1.0[0x353fa74f98]
/usr/lib64/libpython2.4.so.1.0[0x353fa4abd2]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalCodeEx+0x383)[0x353fa95363]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalFrame+0x407f)[0x353fa9405f]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalCodeEx+0x925)[0x353fa95905]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalFrame+0x407f)[0x353fa9405f]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalFrame+0x44a6)[0x353fa94486]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalFrame+0x44a6)[0x353fa94486]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalFrame+0x44a6)[0x353fa94486]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalFrame+0x44a6)[0x353fa94486]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalCodeEx+0x925)[0x353fa95905]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalFrame+0x407f)[0x353fa9405f]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalCodeEx+0x925)[0x353fa95905]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalFrame+0x407f)[0x353fa9405f]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalCodeEx+0x925)[0x353fa95905]
/usr/lib64/libpython2.4.so.1.0[0x353fa4c263]
/usr/lib64/libpython2.4.so.1.0(PyObject_Call+0x10)[0x353fa35f90]
/usr/lib64/libpython2.4.so.1.0[0x353fa3c01f]
/usr/lib64/libpython2.4.so.1.0(PyObject_Call+0x10)[0x353fa35f90]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalFrame+0x220d)[0x353fa921ed]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalFrame+0x44a6)[0x353fa94486]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalCodeEx+0x925)[0x353fa95905]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalFrame+0x407f)[0x353fa9405f]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalCodeEx+0x925)[0x353fa95905]
/usr/lib64/libpython2.4.so.1.0(PyEval_EvalCode+0x32)[0x353fa95952]
/usr/lib64/libpython2.4.so.1.0[0x353fab1ea9]
/usr/lib64/libpython2.4.so.1.0(PyRun_SimpleFileExFlags+0x1a8)[0x353fab3358]
/usr/lib64/libpython2.4.so.1.0(Py_Main+0xa5d)[0x353fab979d]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x352d41d8a4]
python[0x400629]


More information about the lxml-dev mailing list