| commit | 556b9a216f514faae7ddeb712ebb4a1bfa28c929 | |
| author | Johannes Sixt <j6t@kdbg.org> | |
| Sun, 4 Nov 2012 20:39:26 +0000 (4 21:39 +0100) | ||
| committer | Johannes Sixt <j6t@kdbg.org> | |
| Sun, 18 Nov 2012 12:28:13 +0000 (18 13:28 +0100) | ||
| tree | 653cc3b2837130201c954e0a219a5c5a8e317e57 | treesnapshot (tar.gz zip) |
| parent | 25057ccba1448a2a8bf1508d34793de07fe339a0 | commitdiff |
Skip hints about duplicated breakpoints.
When a breakpoint is set at a location that already has a breakpoint, GDB
responds with "Note: breakpoints 3 and 4 also set at pc 0x41d5fa." It
confuses the parser, as if there was a syntax error. As a consequence,
KDbg treats the breakpoint as orphaned, but later it appears also in the
breakpoint list (because GDB did set the breakpoint), so that KDbg actually
keeps two records of the breakpoint. This eventually grows the breakpoint
list exponentially with each restart of the session.
Skip past such lines.
Noticed by Philip Ashmore.
When a breakpoint is set at a location that already has a breakpoint, GDB
responds with "Note: breakpoints 3 and 4 also set at pc 0x41d5fa." It
confuses the parser, as if there was a syntax error. As a consequence,
KDbg treats the breakpoint as orphaned, but later it appears also in the
breakpoint list (because GDB did set the breakpoint), so that KDbg actually
keeps two records of the breakpoint. This eventually grows the breakpoint
list exponentially with each restart of the session.
Skip past such lines.
Noticed by Philip Ashmore.
| kdbg/gdbdriver.cpp | diffblobblamehistory |