[issue5294] pdb "break" command messes up "continue"

Georg Brandl added the comment: Fixed in r83272 with a slightly different patch. Thanks very much for the report! -- nosy: +georg.brandl resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue5294] pdb "break" command messes up "continue"

Swapnil Talekar added the comment: The problem it seems is actually in the bdb module and not in pdb. The set_next function sets the current frame as stopframe but it does not specify the stoplineno. Hence it's always -1. When you do c(ontinue), set_continue just sets botframe as stopframe, i

[issue5294] pdb "break" command messes up "continue"

Petr Viktorin added the comment: It doesn't matter whether the breakpoint is set from within a function or not, but only the module-level frame is affected. import pdb def test(): print ("At line 4") print ("At line 5") print ("At line 6") print ("At line 7") pdb.set_trace()

[issue5294] pdb "break" command messes up "continue"

New submission from Petr Viktorin : Consider this program: import pdb pdb.set_trace() print ("At line 5") print ("At line 6") print ("At line 7") print ("At line 8") print ("At line 9") When set_trace starts the debugger, I set a breakpoint at line 8. When I do that, the continue command star