[lxml-dev] Possible 'freeing null pointer' problem with 'document()' function
Sidnei da Silva
sidnei at enfoldsystems.com
Fri Aug 24 21:01:30 CEST 2007
Ok, I didn't finish setting up my environment on Linux (Paralells
behaving badly today). But I've found some information about
mod_python and C-based Python extensions that seems relevant.
The Xapian folks pointed me out to this piece of documentation, which
hints about using Xapian with mod_python and mentions issues about
multiple interpreters and acquiring locks.
http://svn.xapian.org/trunk/xapian-bindings/python/docs/bindings.html?r1=9201&r2=9202&view=patch
Using the trick described there, setting 'PythonInterpreter
main_interpreter' solves my crash, but leaves me wondering how I can
write a reproducible test case without having more knowledge about
multiple interpreters.
Is that enough information for you to work with Stephan? Maybe it's a
known-issue that just needs to be documented? Or is it a real bug
involving Python resolvers and multiple interpreters?
--
Sidnei da Silva
Enfold Systems http://enfoldsystems.com
Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214
More information about the lxml-dev
mailing list