You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee=Noneclosed_at=<Date2004-11-07.11:37:58.000>created_at=<Date2004-11-07.04:26:18.000>labels= ['library']
title='fix for bug 1055168 (pdb not entering the right frame)'updated_at=<Date2004-11-07.11:37:58.000>user='https://bugs.python.org/isandler'
Bdb.set_trace() assumed that the frame which needs to
be debugged is the caller's frame. This assumption
fails if Bdb_set_trace() is called from inside a
debugger (say from inside of a pdb's set_trace). So now
Bdb.set_trace() accepts an optional parameter
frame_to_debug which allows the caller to specify which
frame needs to be debugged, and pdb is modified to use it..
The original bug report gives an example where the code to
debug was specified from python's shell. I am not quite how
pdb is supposed to behave in this case.. With the patch, it
does seem to enter in the right frame, but it can't list the
code.
The patch does work when the code comes from a file.
That's normal: pdb can never list code that was input on a
console. A coworker of mine (Jeroen Vloothuis) and I
beautified the code a bit, and I checked it in as rev 1.73
of pdb.py and rev 1.47 of bdb.py. Thanks for the patch!
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: