[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
sometime the backtrace of ddd is out of synch with gdb.
From: |
Giuseppe Castagno |
Subject: |
sometime the backtrace of ddd is out of synch with gdb. |
Date: |
Sat, 17 Dec 2005 20:34:20 +0100 |
Hi all,
while debugging openoffice.org I came across the following.
I added the backtrace as printed from gdb (bt command) as an attachement
(atta.ddd).
Notice the frames #8 and #23, it seems that gdb inserts a new line
character in the middle of the frame description, just after the error
printing.
If I use the status|backtrace menu command in ddd I get a frame list
that's synchronous up to and including frame #8, but when I click the
frame #9 the command send to gdb is 'frame 10', that is, there is an
additional frame in the dialog list beetween the #8 and the #9
containing the text ') at objmisc.cxx:1200'. If I click on this
unnumbered frame gdb is issued the command 'frame 9'. In the end, with
the backtrace attached, if I click on frame #40 on the dialog the gdb
command is 'frame 42'.
Thanks for the patience.
Regards,
Giuseppe Castagno.
giuseppe.castagno@gmail.com
atta.ddd
Description: Text document
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- sometime the backtrace of ddd is out of synch with gdb.,
Giuseppe Castagno <=