[issue9064] pdb enhancement up/down traversals

2010-06-27 Thread Georg Brandl
Georg Brandl added the comment: Committed a slightly different patch in r82263. Thanks for the idea! -- nosy: +georg.brandl resolution: -> accepted status: open -> closed ___ Python tracker __

[issue9064] pdb enhancement up/down traversals

2010-06-24 Thread Andrew Valencia
Andrew Valencia added the comment: My bad (new editor session lost the tab setting). Please consider this one with no tabs instead. -- Added file: http://bugs.python.org/file17760/pdb_up3.patch ___ Python tracker

[issue9064] pdb enhancement up/down traversals

2010-06-24 Thread Andrew Valencia
Andrew Valencia added the comment: Debugging tools which have bugs are a real pain... thanks for your comments and attention. Here's another try. With all the loop baggage gone the argument handling really called for factoring out. -- Added file: http://bugs.python.org/file17759/pdb

[issue9064] pdb enhancement up/down traversals

2010-06-24 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc added the comment: Two remarks: - when int(arg) fails, an error message should be printed, like with the function do_commmands(). - the "for" loop seems unnecessary, something like "self.curindex -= nup" should be enough -- ___

[issue9064] pdb enhancement up/down traversals

2010-06-24 Thread Andrew Valencia
Andrew Valencia added the comment: Here's the patch, hopefully updated as requested. Thanks! -- keywords: +patch Added file: http://bugs.python.org/file17758/pdb_up.patch ___ Python tracker ___

[issue9064] pdb enhancement up/down traversals

2010-06-24 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc added the comment: This is a good idea, but tab characters are disallowed in core python code; please replace them with spaces. Then, please provide an "unified" diff patch (with "diff -u"), and name it with the ".patch" extension, this will make it easier to read. --

[issue9064] pdb enhancement up/down traversals

2010-06-23 Thread Andrew Valencia
New submission from Andrew Valencia : In very deep stack traces (like runaway recursion) it can be a pain to get up to the top of the stack to see what kicked it off. I've enhanced up/down to take a numeric argument for the number of positions to traverse, or -1 to go to the top/bottom. Samp