Re: [boost] boost.python problem in release branch (GSoc work)

Subject: Re: [boost] boost.python problem in release branch (GSoc work)
From: Ralf W. Grosse-Kunstleve (rwgk_at_[hidden])
Date: 2009-11-07 16:00:00

Sorry, I took the output from the wrong build. In this build I was using /usr/bin/python instead of a Python compiled from sources. But there was no mix of Python versions.

In the meantime I've sent Haoyu more info based on a Python 2.6.4 debug build.
Ralf

----- Original Message ----
From: Steven Watanabe <watanabesj_at_[hidden]>
To: boost_at_[hidden]
Sent: Sat, November 7, 2009 12:37:19 PM
Subject: Re: [boost] boost.python problem in release branch (GSoc work)

AMDG

Ralf W. Grosse-Kunstleve wrote:
> Sorry for the incomplete report last night. It was very late here.
>
> Below is a valgrind output. This is with Python 2.6.2 compiled from sources under Fedora 8 x86_64. I've also seen the error with Python 2.6.4, I'm pretty sure, but I'll double check. I'll also try compiling everything with debug symbols to get line numbers. I'll let you know what I find.
>
> <snip>
> ==5967== Conditional jump or move depends on uninitialised value(s)
> ==5967==    at 0x36472DB8B6: (within /usr/lib64/libpython2.5.so.1.0)

Are the errors because of mixed python versions?