[C++-sig] Issues with Debug/Release versions of Python and extensions

Roman Yakovenko roman.yakovenko at gmail.com
Fri Feb 2 20:53:59 CET 2007


On 2/2/07, Alexander Eisenhuth <newsuser at stacom-software.de> wrote:
> > Yes. I used Python.Net project for create huge number of tests for
> > code written in
> > Managed C++.
>
> That means you also use a "release exe" and "debug exe" and got
> _CrtIsValidHeapPointer() assertions ?

Python 2.4 release build( standard Python 2.4 setup ), [un]managed
code was built in debug mode.

> >
> >> Ok a straight question, that hopefully anybody can answer.
> >>
> >> Might there appear problems, when I use a standard python Installation
> >> (nodebug-version) on windows to debug a extension (debug-version) ?
> >
> > Except this annoying problem, I didn't have any problem. I was able to debug
> > managed and unmanaged code.
>
> Did you look for compiler switches or pragmas to turn _CrtIsValidHeapPointer() off?

I did not have time to find out what is the exact problem. I just
built release version
with debug information.

-- 
Roman Yakovenko
C++ Python language binding
http://www.language-binding.net/



More information about the Cplusplus-sig mailing list