[issue17697] Incorrect stacktrace from pdb

Changes by Aaron Meurer : -- nosy: +Aaron.Meurer ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue17697] Incorrect stacktrace from pdb

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 PyCo

[issue17697] Incorrect stacktrace from pdb

Changes by Ned Deily : -- stage: -> needs patch versions: +Python 2.7, Python 3.2, Python 3.4 ___ Python tracker ___ ___ Python-bugs-

[issue17697] Incorrect stacktrace from pdb

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)() -> foo('first call') > /Users/rkern/s

[issue17697] Incorrect stacktrace from pdb

Ian Kelly added the comment: The bug also occurs using 32-bit Python 3.3.1 on Windows 7. -- nosy: +ikelly ___ Python tracker ___ ___ P

[issue17697] Incorrect stacktrace from pdb

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 ver