Re: [issue13183] pdb skips frames after hitting a breakpoint and running step

> Georg Brandl added the comment: > > Should be fixed now. Thanks for the commit fix, Georg. The comment on buildbot failures had escaped my attention. Sorry for that. ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/opti

[issue13183] pdb skips frames after hitting a breakpoint and running step

Xavier de Gaye added the comment: Note that now that this issue is fixed, issue 14743 has become more visible. -- ___ Python tracker ___

[issue13183] pdb skips frames after hitting a breakpoint and running step

Georg Brandl added the comment: Should be fixed now. -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing li

[issue13183] pdb skips frames after hitting a breakpoint and running step

Roundup Robot added the comment: New changeset 2644e4ea02d3 by Georg Brandl in branch '2.7': #13183: backport fixes to test_pdb to 2.7 branch http://hg.python.org/cpython/rev/2644e4ea02d3 -- ___ Python tracker ___

[issue13183] pdb skips frames after hitting a breakpoint and running step

Roundup Robot added the comment: New changeset e275a9f7daa9 by Georg Brandl in branch '3.2': #13183: backport fixes to test_pdb to 3.2 branch http://hg.python.org/cpython/rev/e275a9f7daa9 -- ___ Python tracker ___

[issue13183] pdb skips frames after hitting a breakpoint and running step

Antoine Pitrou added the comment: If the failures don't get fixed, the offending commit should be reverted. -- nosy: +pitrou ___ Python tracker ___ _

[issue13183] pdb skips frames after hitting a breakpoint and running step

Xavier de Gaye added the comment: The test has been changed in the default branch by changeset 1b174a117e19. This change replaces the assertIn by a less restrictive assertTrue. These changes should also probably be made in 3.2 and 2.7 and hopefully this will fix the problem in 3.2 and 2.7. The

[issue13183] pdb skips frames after hitting a breakpoint and running step

Charles-François Natali added the comment: All 3.2 and 2.7 buildbots are still broken: http://python.org/dev/buildbot/all/builders/x86 OpenIndiana 3.2/builds/1080 """ == FAIL: test_issue13183 (test.test_pdb.PdbTestCase) ---

[issue13183] pdb skips frames after hitting a breakpoint and running step

Roundup Robot added the comment: New changeset 6c9ce7e34511 by Martin v. Löwis in branch 'default': Issue #13183: Revert 0b53b70a40a0 (reenable test on windows) http://hg.python.org/cpython/rev/6c9ce7e34511 -- ___ Python tracker

[issue13183] pdb skips frames after hitting a breakpoint and running step

Martin v. Löwis added the comment: > But it is strange behavior that "stepping through" enters print in > Windows and does not so in Unix. What's the difference in windows > that could cause this? Not sure if this was expected behavior. On Unix, the codec most likely is UTF-8, which is directly

[issue13183] pdb skips frames after hitting a breakpoint and running step

Senthil Kumaran added the comment: Fixed again with replacing print with pass. But it is strange behavior that "stepping through" enters print in Windows and does not so in Unix. What's the difference in windows that could cause this? Not sure if this was expected behavior. -- _

[issue13183] pdb skips frames after hitting a breakpoint and running step

Roundup Robot added the comment: New changeset 3b2aa777b725 by Senthil Kumaran in branch '2.7': fix windows test failure - issue13183 http://hg.python.org/cpython/rev/3b2aa777b725 New changeset d17ecee3f752 by Senthil Kumaran in branch '3.2': fix windows test failure - issue13183 http://hg.pyth

[issue13183] pdb skips frames after hitting a breakpoint and running step

Martin v. Löwis added the comment: That indeed makes the test pass. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsub

[issue13183] pdb skips frames after hitting a breakpoint and running step

Xavier de Gaye added the comment: My fault :( The call to print is useless for the test, so I suggest to replace it with a plain 'pass' statement. -- ___ Python tracker ___

[issue13183] pdb skips frames after hitting a breakpoint and running step

Martin v. Löwis added the comment: The test fails on Windows. Whereas on Unix, the two step commands produce this output: -> print('1') (Pdb) step 1 --Return-- > /net/pao/export/home/staff/loewis/work/33/bar.py(2)bar()->None -> print('1') (Pdb) step --Return-- > /net/pao/export/home/staff/loew

[issue13183] pdb skips frames after hitting a breakpoint and running step

Senthil Kumaran added the comment: Hello Xavier, Thanks for the explanation. Understood the reason for setting the frame_returning to None. The patch is committed in all python versions and the issue is fixed now. Thanks for the patch and prodding through this. -- Senthil -- resolu

[issue13183] pdb skips frames after hitting a breakpoint and running step

Roundup Robot added the comment: New changeset 96cb47f8142e by Senthil Kumaran in branch '3.2': issue13183 - Fix pdb skipping frames after hitting a breakpoint and running step. Patch by Xavier de Gaye http://hg.python.org/cpython/rev/96cb47f8142e New changeset 5ea23739e9ba by Senthil Kumaran

[issue13183] pdb skips frames after hitting a breakpoint and running step

Xavier de Gaye added the comment: Hi Senthil, Thanks for your help with this issue. self.frame_returning is both a flag to indicate that we are returning from the current frame and a value (the current frame). We need both as set_step() (the method invoked when the user runs the step command)

[issue13183] pdb skips frames after hitting a breakpoint and running step

Senthil Kumaran added the comment: Hello Xavier, This issue required some tracing through the calls and I see the problem that you have mentioned and patch fixes the problem. One comment on the patch, for the tests in the module, this line - self.frame_returning = None does not seem to ha

[issue13183] pdb skips frames after hitting a breakpoint and running step

Changes by Tshepang Lekhonkhobe : -- nosy: +tshepang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue13183] pdb skips frames after hitting a breakpoint and running step

Senthil Kumaran added the comment: It's an interesting issue. Thanks for the report and patch, Xavier. I am setting patch to needing review. -- keywords: +needs review -patch nosy: +orsenthil versions: +Python 2.7, Python 3.3 ___ Python tracker

[issue13183] pdb skips frames after hitting a breakpoint and running step

Xavier de Gaye added the comment: This message is just a reminder that this 4 months old issue raises the point that the step command in pdb is broken. A patch and test case have been proposed. No comment so far. As the author of pyclewn, a Vim front end to pdb and gdb, I would be grateful for

[issue13183] pdb skips frames after hitting a breakpoint and running step

Changes by Meador Inge : -- nosy: +meador.inge ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue13183] pdb skips frames after hitting a breakpoint and running step

Changes by Georg Brandl : -- nosy: +georg.brandl ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue13183] pdb skips frames after hitting a breakpoint and running step

Xavier de Gaye added the comment: Uploaded restore_trace.py27.patch with a fix and test case for python 2.7. -- Added file: http://bugs.python.org/file23419/restore_trace.py27.patch ___ Python tracker

[issue13183] pdb skips frames after hitting a breakpoint and running step

Xavier de Gaye added the comment: Uploaded restore_trace_2.patch that improves the test case. -- Added file: http://bugs.python.org/file23418/restore_trace_2.patch ___ Python tracker __

[issue13183] pdb skips frames after hitting a breakpoint and running step

Changes by Xavier de Gaye : -- type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue13183] pdb skips frames after hitting a breakpoint and running step

New submission from Xavier de Gaye : Pdb skips frames after hitting a breakpoint and running step commands that walk back the frame stack. Run the following two tests with the two files named foo.py and bar.py: === foo.py from bar import bar def