On Sat, 6 Aug 2011 04:23:26 -0600, Aaron Meurer <[email protected]> wrote: > So I'm coming along with the variable wrapping stuff, but I'm running > into some problems that I think are the result of my ignorance of how > urwid and the majority of the pudb code works. > > Anyway, instead of wrapping properly, it crashes. Do you have any > suggestions on how to use pudb to debug itself? Ideally, I would like > to run the local pudb (which has the broken code) from within the > system pudb (which doesn't). Just post-mortem is fine. > > Otherwise, debugging pudb itself is ironically very difficult. Print > statements don't even work
I've never tried any such thing, but I've definitely felt your pain. What I've usually done is used prints to a different terminal. ls -lah /proc/$$/fd will tell you what pseudoterminal an xterm is attached to, and then you can open that in a global variable and use it for debug output. Pudb's ability to debug itself mostly hinges on bdb's ability to do the same, and I've found it mostly incapable of doing so. (but I haven't tried very hard) Good luck, and hope this helps, Andreas
pgpLxVGZQwGAb.pgp
Description: PGP signature
_______________________________________________ Pudb mailing list [email protected] http://lists.tiker.net/listinfo/pudb
