New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tokenize the source to manage Pdb breakpoints #59118
Comments
Pdb behavior is not consistent with GNU gdb behavior when setting a Pdb performance: Pdb breakpoint management problems: Pdb rejects setting a breakpoint in a function or method defined in a $ python
Python 3.2.2 (default, Dec 27 2011, 17:35:55)
[GCC 4.3.2] on linux2
Type "help", "copyright", "credits" or "license" for more
information.
>>> import pdb; pdb.run('def foo(): pass')
> <string>(1)<module>()
(Pdb) break asyncore.close_all
Breakpoint 1 at /usr/local/lib/python3.2/asyncore.py:580
(Pdb) break logging.info
*** The specified object 'logging.info' is not a function or was
not found along sys.path. When a breakpoint is set at the line number of a function definition, Use tokenize: The attached patch implements this solution with std lib tokenize:
|
Uploaded pdb_default_2.patch.
This is not correct. One should read instead:
This is fixed as well in both patches. |
Attached patch pdb_lnotab.patch uses lnotabs (see The patch fixes issues 6322, 14789, 14792, 14795, 14808. The local trace function is only set on functions where a breakpoint is |
See also how this is fixed at |
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: