On Tue, 2011-10-11 at 15:00 +0400, Dmitry Trofimov wrote:
Hi!
Does it supposed to work on windows?
For me it doesn't on win7 64bit.
Calling PyRun_SimpleString results to
Program received signal SIGSEGV, Segmentation fault.
0x1e003ad5 in python26!PyImport_GetModuleDict () from
C:\Windows\system32\python26.dll
The program being debugged was signaled while in a function called from GDB.
GDB remains in the frame where the signal was received.
To change this behavior use "set unwindonsignal on".
Evaluation of the expression containing the function
(python26!PyRun_SimpleString) will be abandoned.
When the function is done executing, GDB will silently stop.
FWIW, I've never run it on Windows; I don't have a Windows machine with
a suitable toolchain installed.
I can think of various things that could have gone wrong: gdb needs to
have correct debug data available in order to inject the correct calls
into the thread it connects to. If that's missing, it has to guess at
the argument sizes and calling conventions, and if its guess is
incorrect, it will likely lead to a segfault in the process you attach
to. But it could be something entirely different, alas.
Sorry not to be more help
Dave