The Very High Layer and friends

[G. David Kuhlman]

Since we're talking about .dll's, I'll assume that we are on WinNT. 
The source code distribution comes with project files for MS Visual
C++.  You can build the debug version of the .dll, link the .lib
with your program, then debug from your embedded app into the
Python source code using the MS debugger.  Make sure, as mentioned
by Gordon McMillan, to keep the code generation consistent.  Use
"Debug Multithreaded DLL" for debugging.

  - Dave


Thomas S. Strinnhed <thstr at serop.abb.se> wrote:
> Thank you, makes sense.

> But how do I solve it? Can't really figure out from your reply if
> the problem lies in python15.dll or elsewhere. Can it be "tracked"
> in runtime?

> Regards
>  -- Thomas S. Strinnhed, thstr at serop.abb.se

> Gordon McMillan wrote:
> > 
> > The most likely cause is mismatching c runtime libs. The stock
> > python15.dll uses "Multithreaded DLL". You're using the right kind of
> > FILE, but you've opened it in one c runtime lib, and the other ends
> > up with a bad pointer.
> > 
> > - Gordon