[issue9919] gdbinit lineno result is one line in excess

Georg Brandl added the comment: Right. Fixed in r86134. Thanks :) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscr

[issue9919] gdbinit lineno result is one line in excess

qpatata added the comment: I'm sorry, I've not explained correctly. I'm wondering if the addition of the \n is ok or not, taken into account that it breaks the format of the "pyframe" macro output. It could be better to keep the older version (without the \n"). Kind regards. -- ___

[issue9919] gdbinit lineno result is one line in excess

Georg Brandl added the comment: If you look at the commit, you'll see that I already added that newline. Thanks anyway :) -- ___ Python tracker ___

[issue9919] gdbinit lineno result is one line in excess

qpatata added the comment: Hi, Thanks for the fix. I'm wondering if it is valid to add a "\n" in the "lineno" print. This macro is called by other ones, like pyframe, that have their own format specifiers. Kind regards. -- ___ Python tracker

[issue9919] gdbinit lineno result is one line in excess

Georg Brandl added the comment: Patch looks good, committed in r85768. -- nosy: +georg.brandl resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue9919] gdbinit lineno result is one line in excess

Changes by Alexander Belopolsky : -- components: +Demos and Tools versions: +Python 3.2 -Python 2.5 ___ Python tracker ___ ___ Python-b

[issue9919] gdbinit lineno result is one line in excess

qpatata added the comment: Well, me also I'm not expert in gdb. Solution looks nice and previous testcase now gives the correct answer. Thanks a lot for your help. -- ___ Python tracker __

[issue9919] gdbinit lineno result is one line in excess

Amaury Forgeot d'Arc added the comment: OK, I reproduce the issue. It is now clear to me as well that r39492 was slightly wrong: the replacement of "break" should avoid to execute the end of the loop. The following patch fixes the issue for me, can someone with better gdb knowledge check it?

[issue9919] gdbinit lineno result is one line in excess

qpatata added the comment: Hello, Thanks for your colaboration. Starting by the following python file, called "prueba.py": > cat prueba.py import time def bar(): time.sleep(10); print "hello"; def foo(): while True: bar(); foo(); Open a gdb session with python2-6 as targe

[issue9919] gdbinit lineno result is one line in excess

Amaury Forgeot d'Arc added the comment: Can you show an example which shows an incorrect lineno? -- nosy: +amaury.forgeotdarc ___ Python tracker ___ _

[issue9919] gdbinit lineno result is one line in excess

New submission from qpatata : Thanks a lot to all python teams for your excel.lent work. When latest version of gdbinit macros is used to debug with gdb a python 2.4 session, the result from lineno macro seems one line more than the correct one. If we compare the gdb macro: define lineno