Comments on: Embedded Debugging

By: Gyan

Gyan — Thu, 08 Mar 2012 13:32:42 +0000

I am getting following error -

ImportError: No module named _socket

I see a post that we need _socket.pyd and _socket_d.pyd

Where can I get these?

By: Marc Breyers

Marc Breyers — Wed, 29 Feb 2012 16:41:31 +0000

Such a are good all over again routines wherein means that we can take it easy the actual spinal cord as well as sleep thoroughly without the practical experience in regard to overload of your all over again.

By: Thouis Jones

Thouis Jones — Fri, 16 Sep 2011 13:19:44 +0000

I should be more clear. I can call start_embedded_debugger() in an “except:” clause, can connect to the debugee, but cannot find how to debug the exception being handled.

By: Thouis Jones

Thouis Jones — Fri, 16 Sep 2011 12:55:18 +0000

I’d like to use rpdb2 to debug worker processes in a multiprocessing application. I can’t seem to figure out how to start the debugger in multiple processes, though. I know about “fork parent” and “fork child”, but what I’d really like is for both processes to end up running the debugger.

I tried to start debugging in the children after the fork (in the target of multiprocessing. Process()) using rpdb2.start_embedded_debugger(), but haven’t had any luck. Exceptions seem to just pass by the rpdb2 excepthook.

Any suggestions?

By: Perry

Perry — Tue, 14 Sep 2010 20:58:50 +0000

i am trying to attach to a python script used by gdb under eclipse to pretty print qt4. I see the .py file in the attach window of winpdb, with the correct path, but when i click it, it says:

Failed to attach to foo.py
Failed to find script

any idea what i am doing wrong? I was so happy to get it running so far =8(

By: Tom Gaulton

Tom Gaulton — Thu, 09 Sep 2010 09:45:18 +0000

I’m trying to use winpdb to debug a python scripts embedded in my own 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

By: Henrik Vendelbo

Henrik Vendelbo — Sat, 01 May 2010 18:33:07 +0000

This doesn’t seem to work on PyPy

Are you forgetting to close files ?

I get OSError, [Errno 24] Too many open files trying to use it with PyPy 1.1 on OS X

By: vit

vit — Tue, 05 Jan 2010 23:24:30 +0000

Update: after some poking around I managed to make it work by creating a source provider that would read chrome:// URLs. I’m happy now! Thanks for great work!
By the way, it looks like the documentation on this page is not up do date.

By: vit

vit — Tue, 05 Jan 2010 22:23:04 +0000

Hi,

I was trying to use winpdb to debug XULRunner/pyXPCOMExt application, but whenever I’m connecting to the script, I’m getting the following message:

“Failed to load source file ‘chrome://appname/content/main.py’ from debuggee.
You may continue to debug, but you will not see source lines from this file.”

The Namespace/Threads/Stack panels are populated with correct inspectable data though. I was trying to load the source file and set a breakpoint, but winpdb would not stop on the breakpoint in this case.

By: Tomeu Vizoso: A week at LATU (part II): Developing with Sugar | Full-Linux.com

Thu, 31 Dec 2009 07:15:22 +0000

[...] when a debugger is needed pdb is a good equivalent to gdb. If you prefer a graphical debugger, winpdb works well and also allows you to attach to a running [...]