This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] Crash sourcing Python script on Windows
> Date: Thu, 29 Sep 2011 10:38:51 +0200
> From: Kai Tietz <ktietz70@googlemail.com>
> Cc: Joel Brobecker <brobecker@adacore.com>, maillist-gdbpatches@barfooze.de,
> gdb-patches@sourceware.org
>
> The issue here is not the definition of the FILE type itself in this
> case. The problem is that python (if built with VC) uses different
> runtime-version (msvcr100.dll or lower), but mingw uses by well know
> reasons the msvcrt.dll. So by loading this python-DLL into a
> mingw-built executable, we have two different runtimes at the same
> time.
Thanks, this makes sense.
What are the reasons that we build GDB against msvcrt.dll?
> By the way, the same issue can lead also for different C-runtime
> functions pretty funny results.
Exactly. If we have such an incompatibility once python's DLL is
loaded, it can lead to similar crashes elsewhere. So, unless we can
find a way of linking against msvcrNNN.dll or build our own Python
with MinGW, it sounds like using Python on Windows is unsafe?