I’m trying to use winpdb to debug a python scripts embedded in my own C++ application. I can connect and view the callstack, globals, etc. initially but I’m having problems getting breakpoints to halt execution.
When my breakpoint is hit the status bar in winpdb briefly switches to ‘WAITING AT BREAKPOINT’ then immediately switches back to ‘RUNNING’. Occasionally (perhaps 1 in 50 times) the breakpoint works correctly, however if I try to use ‘Step Into’ or Next’ the status switches back to ‘RUNNING’ again.
Has anyone else had this problem? Is there something that might be happening in my application that causes it? The scripts are executed using PyRun_SimpleString() and always execute on the same thread I called rpdb2.start_embedded_debugger() from.
Any help or advice appreciated, the tool looks to be exactly what I need and is tantalizingly close to working.