Access violation in MSVCRT.DLL when attempting to use Python..

[Mark Hammond]

"Jason Maskell" <backov at nospam.csolve.net> wrote in message
news:iogp4.530$M73.526 at 198.235.216.4...
> I have finally got all my code ported over to VC++, and now I seem
to be
> having a strange problem.. I am testing out my glue code with simple
test
> cases - in this case, I run this
>
>
...

> Which sets a couple properties of that interface element. The
function works
> fine, decreases all the references that it needs to (I believe) and
then

My bet is that your belief is wrong :-)

> clue what is going on. Can anyone give me a quick pointer how to set
up VC
> so that I can trace into the python source? Do I need to link to the
python
> debug dll?

Yes - you should simply be able to build the debug version of your
extension/program.  This should automatically bring in python15_d.dll
instead of python15.dll.  However, be warned - you will need to have
debug versions of _all_ your Python DLLs.

FWIW, registered users of the win32all extensions get binary _d
versions of the core Python DLL and all the win32 related DLLs.

Mark.