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: pdb sometimes sets breakpoints in the wrong location
Type: Stage:
Components: Library (Lib) Versions: Python 2.4
process
Status: closed Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: isandler
Priority: normal Keywords:

Created on 2004-03-31 17:09 by isandler, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (2)
msg20398 - (view) Author: Ilya Sandler (isandler) Date: 2004-03-31 17:09
If one attempts to set a breakpoint in one line function:
e.g for this code:

def f(x): return x*x

z=23

pdb silently sets a breakpoint on the line right after
the function definition (i.e. outside the function body!):

../python pdb.py.v1.66 pdb_one_line_func 
> <string>(1)?()
(Pdb) b f
Breakpoint 1   /src/Lib/pdb_one_line_func:3
(Pdb) c
> /src/Lib/pdb_one_line_func(3)?()
-> z=23

It's probably acceptable to limit pdb breakpoints to
multiline functions, but i don't think, it's acceptable
to create wrong breakpoints.

Note: that anyone attempting to fix this should also
take a look at bug 875404 (global statment causes
breakpoints..), as both bugs are caused by
pdb.checkline() logic
msg20399 - (view) Author: Ilya Sandler (isandler) Date: 2004-03-31 17:11
Logged In: YES 
user_id=971153

Sorry, accidentally resubmitted the bug
History
Date User Action Args
2022-04-11 14:56:03adminsetgithub: 40109
2004-03-31 17:09:04isandlercreate