Re: problem using python-ldap under fcgi

[Michael S. <mi...@st...>]

Matt Bartolome wrote:
> My apologies on the wild goose chase but after using valgrind on my
> fcgi process it is python cx_Oracle (would have never guessed that!)
> which triggers the segmentation fault when ldap.initialize() is
> called. Why it does this is beyond me but a simple alteration of my
> code makes the problem go away completely. I was creating a global
> oracle db cursor which I'm now creating inside the functions that use
> it.
> 
> I'm not sure about the glib c error and patch now. Using the original
> release without modification works so I will leave it at that.

Glad you figured out what the issue was. It's good if you don't run a 
patched version of python-ldap. In general and thanks to the 
contributors who provided patches in the past python-ldap seems fairly 
stable.

But let's look at the blog entry which convinced you to try patching 
python-ldap (see 
http://www.notes.xythian.net/2007/10/24/python-cdb-032-52ubuntu2-with-python-25-causes-double-free-corruption-crash-on-dealloc/):

"Some other searching suggests that python-cdb’s use of PyMem_DEL is no 
longer recommended."

That's pretty unprecise, not even a single URL.

But if somebody can add more detailed information to this it could be 
helpful to dive into this. IMO an admirable goal of python-ldap is not 
to fall back behind what's considered current best practice when writing 
extension modules for CPython.

Ciao, Michael.