Changes by Aaron Meurer asmeu...@gmail.com:
--
nosy: +Aaron.Meurer
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17697
___
___
Python-bugs-list
Xavier de Gaye added the comment:
The call to set_trace() installs a local trace function on all the
frames of the stack, including on the oldest frame, i.e. the module
level frame. This causes the invocation of frame_settrace() in
frameobject.c and the module frame f_lineno is evaluated by
New submission from Don Allen:
Give the attached file execute permission and run it. At the first breakpoint,
the backtrace will be correct. Continue. At the second breakpoint, a backtrace
will show the foo('first call') on the stack when, in fact, the call came from
foo('second call'), as
Ian Kelly added the comment:
The bug also occurs using 32-bit Python 3.3.1 on Windows 7.
--
nosy: +ikelly
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17697
___
Ned Deily added the comment:
On python-list, Robert Kern used where to demonstrate the problem:
$ python pdbbug.py
first call
--Return--
/Users/rkern/scratch/pdbbug.py(4)foo()-None
- pdb.set_trace()
(Pdb) where
/Users/rkern/scratch/pdbbug.py(5)module()
- foo('first call')
Changes by Ned Deily n...@acm.org:
--
stage: - needs patch
versions: +Python 2.7, Python 3.2, Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17697
___
