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.

classification
Title: after continue, Pdb stops at a line without a breakpoint
Type: behavior Stage:
Components: Library (Lib) Versions: Python 3.2, Python 3.3, Python 2.7
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: georg.brandl, xdegaye
Priority: normal Keywords: patch

Created on 2012-05-12 13:54 by xdegaye, last changed 2022-04-11 14:57 by admin.

Files
File name Uploaded Description Edit
pdb_default.patch xdegaye, 2012-05-12 13:54 review
Messages (2)
msg160470 - (view) Author: Xavier de Gaye (xdegaye) * (Python triager) Date: 2012-05-12 13:54
In the following test run with python on the current head of the
default branch, Pdb stops at line 3 where there is no breakpoint after
two breakpoints have been set on the same function (setting two bps on
the same location is useful, for example one bp to print a value without
stopping and the other one with an ignore count).

===   main.py   =================================
def bar():
    x = 1
    x = 2

bar()
=================================================
$ python -m pdb main.py 
> /path_to/main.py(1)<module>()
-> def bar():
(Pdb) import sys; print(sys.version)
3.3.0a3+ (default:4e9680570be8, May 11 2012, 12:09:15) 
[GCC 4.3.2]
(Pdb) break bar
Breakpoint 1 at /path_to/main.py:1
(Pdb) break bar
Breakpoint 2 at /path_to/main.py:1
(Pdb) continue
> /path_to/main.py(2)bar()
-> x = 1
(Pdb) continue
> /path_to/main.py(3)bar()
-> x = 2
(Pdb) quit
=================================================

The attached patch fixes the problem. This patch also fixes the
following problems that are caused by the same bug:

    * when more than one breakpoint is set on the same line, only the
      command of the first effective breakpoint is run, and only the
      hit count and the ignore count of the first effective breakpoint
      are updated

The patch includes a test case for all those problems.
msg161571 - (view) Author: Xavier de Gaye (xdegaye) * (Python triager) Date: 2012-05-25 11:54
Parsing the modules source seems a better way to fix this problem, see issue 14913.
History
Date User Action Args
2022-04-11 14:57:30adminsetgithub: 58994
2012-05-25 11:54:29xdegayesetmessages: + msg161571
2012-05-18 17:47:52terry.reedysetnosy: + georg.brandl
2012-05-12 13:54:12xdegayecreate