Matt Bartolome wrote:
> I'll take a stab at this. I'll give you fair warning though that I
> don't know much about C. It looks like the modifications would be
> fairly straight forward though given I can find the recommended usage
> and documentation. I left off at the type cast build warnings so I
On Wed, Aug 27, 2008 at 1:30 PM, Michael Ströder <[EMAIL PROTECTED]> wrote:
> 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.initi
Michael Ströder <[EMAIL PROTECTED]> writes:
> 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 sugg
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
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
Matt Bartolome wrote:
> Hey Michael. Thank you for your response. I modified LDAPObject.c and
> ldapcontrol.c to use the solution described here:
>
> https://bugs.launchpad.net/ubuntu/+source/python-cdb/+bug/157251
>
> Looks like it is something specific to glibc in ubuntu and the
> "recommended"
