This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author donaldcallen
Recipients donaldcallen
Date 2013-04-11.15:07:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1365692859.49.0.652230897549.issue17697@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2013-04-11 15:07:39donaldcallensetrecipients: + donaldcallen
2013-04-11 15:07:39donaldcallensetmessageid: <1365692859.49.0.652230897549.issue17697@psf.upfronthosting.co.za>
2013-04-11 15:07:39donaldcallenlinkissue17697 messages
2013-04-11 15:07:39donaldcallencreate