[issue14913] tokenize the source to manage Pdb breakpoints

Changes by Andrew Svetlov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue14913] tokenize the source to manage Pdb breakpoints

Xavier de Gaye added the comment: See also how this is fixed at http://code.google.com/p/pdb-clone/source/detail?r=6b342324ebdc4558b83b9391e34478c1fa0752db -- ___ Python tracker

[issue14913] tokenize the source to manage Pdb breakpoints

Changes by Éric Araujo : -- nosy: +georg.brandl versions: +Python 3.4 -Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue14913] tokenize the source to manage Pdb breakpoints

Xavier de Gaye added the comment: Attached patch pdb_lnotab.patch uses lnotabs (see Objects/lnotab_notes.txt) to find the actual breakpoint line number and parses the module source with tokenize to find the set of function and fully qualified method names in a module. The patch fixes issues 6322

[issue14913] tokenize the source to manage Pdb breakpoints

Xavier de Gaye added the comment: Uploaded pdb_default_2.patch. This new patch fixes the previous patch that fails to stop at breakpoints set in nested functions, and extends the previous patch in allowing breakpoints outside function and method definitions. > When a breakpoint is set at the li

[issue14913] tokenize the source to manage Pdb breakpoints

New submission from Xavier de Gaye : Pdb behavior is not consistent with GNU gdb behavior when setting a breakpoint on an empty line, a comment or a multi-line statement (the breakpoint is ignored by pdb on a non-first line of a multi-line statement and rejected on empty lines or comment lines).