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 xdegaye
Recipients georg.brandl, xdegaye
Date 2012-05-11.09:00:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1336726836.83.0.687440308356.issue14743@psf.upfronthosting.co.za>
In-reply-to
Content
The previous patch only fixed the problem when the debugger is started
from its main function. Uploaded new patch
pdb_botframe_default_3.patch that fixes pdb.main and the pdb.run*
function.

This patch also corrects pdb.runcall(): in the following session, the
3.1 debugger starts the debugging session at the second line of foo()
and not at the --Call-- event. A test case for this problem is also
included in the patch.


===   main.py   =================================
import pdb, sys
print(sys.version)

def foo():
    pass

pdb.runcall(foo)
=================================================
$ python3.1 main.py
3.1.2 (r312:79147, Apr  4 2010, 17:46:48) 
[GCC 4.3.2]
> /path_to/main.py(5)foo()
-> pass
(Pdb) quit
=================================================
History
Date User Action Args
2012-05-11 09:00:36xdegayesetrecipients: + xdegaye, georg.brandl
2012-05-11 09:00:36xdegayesetmessageid: <1336726836.83.0.687440308356.issue14743@psf.upfronthosting.co.za>
2012-05-11 09:00:36xdegayelinkissue14743 messages
2012-05-11 09:00:36xdegayecreate