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 (withou
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.
--
_
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
<http://bugs.python.org/i
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 se
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
