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.

Title: pdb.set_trace should go up one more frame
Type: Stage:
Components: Library (Lib) Versions:
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: isandler, jlgijsbers
Priority: normal Keywords:

Created on 2004-10-27 09:21 by jlgijsbers, last changed 2022-04-11 14:56 by admin. This issue is now closed.

File name Uploaded Description Edit
pdb-set_trace-session jlgijsbers, 2004-10-27 09:21
Messages (3)
msg22890 - (view) Author: Johannes Gijsbers (jlgijsbers) * (Python triager) Date: 2004-10-27 09:21
Calling pdb.set_trace() calls Bdb.set_trace, which
makes the debugger enter inside pdb.set_trace (see the
attached console session for details). It should enter
at the stack frame calling pdb.set_trace().

I can fix this, but I don't mind if someone else does. 
msg22891 - (view) Author: Ilya Sandler (isandler) Date: 2004-11-07 04:30
Logged In: YES 

I just submitted a patch 1061767 which should fix this problem
msg22892 - (view) Author: Johannes Gijsbers (jlgijsbers) * (Python triager) Date: 2004-11-07 11:38
Logged In: YES 

Fixed by applying #1061767.
Date User Action Args
2022-04-11 14:56:07adminsetgithub: 41089
2004-10-27 09:21:42jlgijsberscreate