New submission from Andrew Valencia :
Build with -DLLTRACE, then:
>>> __lltrace__ = 1
>>> a = [1, 2, 3]
0: 100, 0
push 1
3: 100, 1
push 2
6: 100, 2
push 3
9: 103, 3
pop 3
pop 2
pop 1
push [1, 2, 3]
12: 90, 0
pop [1, 2, 3]
15: 100, 3
push None
18: 83
pop None
>>>
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/b
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
<http://bugs.python.org/i
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/file
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
<http://bugs.python.org/issue9
