Suggestions?
Post the 10-line program here, so others can verify whether it is a bug.
#! /usr/bin/env python3
import pdb
def foo(message):
print(message)
pdb.set_trace()
foo('first call')
foo('second call')
Stick this in an file with execute permission and run it. At
On Tuesday, April 9, 2013 6:17:28 PM UTC-4, Ned Deily wrote:
In article a34e8251-85df-4486-b5a1-72eb2bb9f...@googlegroups.com,
donallen wrote:
I am I've developed an application in Python 3.3.1 (on an up-to-date 64-bit
Arch Linux system) and am attempting to use pdb to debug it.
I am I've developed an application in Python 3.3.1 (on an up-to-date 64-bit
Arch Linux system) and am attempting to use pdb to debug it. I am getting
incorrect stack traces. I've made up a little 10-line program that illustrates
the problem and I attempted to register on the bug-tracker site,
