> It all runs great in the "Debug" configuration, but
> everything gets scary when I switch to "Release".
My suggestion would be to turn on debug information
for the release build.
That would at least let you run the release build inside
the debugger, allowing you to see the call stack of the
off
I'm embedding a Python interpreter into a project, and compiling with
MSVC. It all runs great in the "Debug" configuration, but everything
gets scary when I switch to "Release".
I've read about things that can go wrong when you use the wrong runtime
library when compiling a program that uses Pyth
