report at bugs
Nov 24, 2009, 4:53 AM
Post #1 of 1
(195 views)
Permalink
|
|
[issue5294] pdb "break" command messes up "continue"
|
|
Swapnil Talekar <swapnil.st [at] gmail> 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, if there are no breakpoints.
Hence, stop_here wrongly returns True on every line event. To rectify
this, set_next should also specify stoplineno for the stopframe and this
should be checked in stop_here before returning True. Here is the patch.
----------
nosy: +swapnil
type: -> behavior
Added file: http://bugs.python.org/file15393/bdbdiff
_______________________________________
Python tracker <report [at] bugs>
<http://bugs.python.org/issue5294>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com
|
