On Fri, 2008-08-01 at 08:47 +0200, Stefan Behnel wrote:
Hi,
John Krukoff wrote:
Okay, can only get it to crash when first signing a document using libxmlsec, so I suppose I'll simply assume that the two libraries use the error log in incompatible ways.
could you check if this patch makes it work better for you? It basically restricts XSLT error logging to the lifetime of an XSL transformation.
Stefan
I still need to compile lxml with -ggdb, where do I stick that in the setup.py/makefile? Interestingly, this is after I've switched to calling an external C# program to do my xml signing, and am no longer using libxmlsec. But, anyway, still crashed with the patch for me: Core was generated by `/usr/bin/python -tt ./Adapter.py'. Program terminated with signal 11, Segmentation fault. #0 0xb774b740 in __pyx_f_4lxml_5etree__forwardError () from /usr/lib/python2.5/site-packages/lxml-2.1.1-py2.5-linux-i686.egg/lxml/etree.so (gdb) bt #0 0xb774b740 in __pyx_f_4lxml_5etree__forwardError () from /usr/lib/python2.5/site-packages/lxml-2.1.1-py2.5-linux-i686.egg/lxml/etree.so #1 0xb774bb12 in __pyx_f_4lxml_5etree__receiveXSLTError () from /usr/lib/python2.5/site-packages/lxml-2.1.1-py2.5-linux-i686.egg/lxml/etree.so #2 0xb76baef9 in xsltPrintErrorContext () from /usr/lib/libxslt.so.1 #3 0xb76bb091 in xsltTransformError () from /usr/lib/libxslt.so.1 #4 0xb76dd434 in xsltValueOf () from /usr/lib/libxslt.so.1 #5 0xb76da5ba in ?? () from /usr/lib/libxslt.so.1 #6 0x0878e718 in ?? () #7 0x08432c60 in ?? () #8 0x0878ec78 in ?? () #9 0x0878f6f8 in ?? () #10 0x00000000 in ?? () Fortunately, I've been able to simplify my crash conditions somewhat, so the valgrind log is significantly shorter. Looks like I'll need to find some time to work on that test case after all. -- John Krukoff <jkrukoff@ltgc.com> Land Title Guarantee Company