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 verified by the printed message.
I am running this on an up-to-date 64-bit Arch Linux system. Python 3.3.1.
----------
components: Library (Lib)
files: python_bug.py
messages: 186561
nosy: donaldcallen
priority: normal
severity: normal
status: open
title: Incorrect stacktrace from pdb
type: behavior
versions: Python 3.3
Added file: http://bugs.python.org/file29777/python_bug.py
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue17697>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
