Comments on: Embedded Debugging

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 [...]

By: araud

araud — Tue, 15 Dec 2009 14:14:28 +0000

Did anyone managed to attach to local process from console?

I am under windows trying this scenario:
c:/temp/test.py contains:
import rpdb2; rpdb2.start_embedded_debugger(”123″)
I run it by double-clicking.
A can attach manually thru gui. But can’t get command line working:
winpdb –attach=test.py –pwd=123 –host=127.0.0.1

All I receive in return is help message…

Thank you!

By: Laurent

Laurent — Sat, 21 Nov 2009 00:25:58 +0000

Ha just found howto make my thread appears.
I’ve added as suggested in your doc:
rpdb2.settrace()

in the thread’s run loop.

And now I see them!

The only question that remains is that they where invoked via threading module
so i suspect they were not detected due to post debugger invocation.

By: Laurent

Laurent — Sat, 21 Nov 2009 00:10:23 +0000

Hi nir,
I’ve just trtied embedded debugger and it works quite well.
I’ve got only one issue:
My app invoke some thread at startup.
If I debug my app like “winpdb myapp”. I can debug them.
On the other side I embed the debugger it could not see the previously invoked thread.
Is there a way to declare the threads to the embedded debugguer, so it could track them?

By: Python Dev Environment - Syntext Forums - Serna Enterprise XML Editor, Serna Free XML Editor

Mon, 29 Jun 2009 22:24:51 +0000

[...] Python interpreters. I’ll give it a try with Serna, but wondered if anyone has tried this already. Winpdb - A Platform Independent Python Debugger Embedded Debugging Regards, [...]

By: fonsch

fonsch — Sat, 25 Apr 2009 06:52:18 +0000

Thanks for the quick reply nir. Upgrading winpdb didn’t help, I still get the same error. I’ll post my question at the Google group (feel free to remove my posts here if they’re out of place )

By: nir

nir — Sat, 25 Apr 2009 02:47:21 +0000

fonsch,

Ubuntu 9.04 has an old outdated package of Winpdb. Try the latest version from this website and let me know if the problem still exists:
http://winpdb.org/download/

Also please use the Winpdb Google group to communicate on this issue:
http://groups.google.com/group/winpdb

Thanks,
Nir