Dear Diez:
I see. I appreciate your help really.
best regards
fang
--
http://mail.python.org/mailman/listinfo/python-list
fang wrote:
> Dear Diez:
>
> It is attaching a C-debugger to python. I can attach python-
> debugger(for example:wingIDE) to c-debugger(for example:VS2008), but I
> cannot attach VS2008 to wingIDE. I need both python statement and c
> statement can be single-step debugged.
AFAIK that's not possi
Dear Diez:
It is attaching a C-debugger to python. I can attach python-
debugger(for example:wingIDE) to c-debugger(for example:VS2008), but I
cannot attach VS2008 to wingIDE. I need both python statement and c
statement can be single-step debugged.
best regards
fang
--
http://mail.python.org/ma
[EMAIL PROTECTED] schrieb:
dear Diez:
I need step into c function in extending module(DLL) when debugging
the script. and I want Single-step debugging the extend module itself,
but python script Launched The whole process.
That is exactly what attaching a C-debugger to python will give you.
dear Diez:
I need step into c function in extending module(DLL) when debugging
the script. and I want Single-step debugging the extend module itself,
but python script Launched The whole process.
best regards
fang
--
http://mail.python.org/mailman/listinfo/python-list
[EMAIL PROTECTED] schrieb:
dear all:
I have searched the debug informations of many python's IDE, but I
cannot find the method about debuging the extend module written in
Visual studio 2008 on windows.
The wingIDE tell me that we can debug the extend module on linux, but
cannot on windows. and u
dear all:
I have searched the debug informations of many python's IDE, but I
cannot find the method about debuging the extend module written in
Visual studio 2008 on windows.
The wingIDE tell me that we can debug the extend module on linux, but
cannot on windows. and using wingdbstub.py we can emb
