| commit | 2365649e316f3cec36ef7dd29b6f5ba780ecb8df | |
| author | Johannes Sixt <j6t@kdbg.org> | |
| Fri, 25 Feb 2011 21:57:02 +0000 (25 22:57 +0100) | ||
| committer | Johannes Sixt <j6t@kdbg.org> | |
| Mon, 28 Feb 2011 21:49:00 +0000 (28 22:49 +0100) | ||
| tree | 86a0c11ac2000fb22da7e77e8c4fc8ad38a4197a | treesnapshot (tar.gz zip) |
| parent | fd891a858c80b05bef75b3c93babb19a916759bf | commitdiff |
Treat continuation lines in scalar register values.
If GDB cannot print the cooked value of a scalar register on the current
line, it places is on the next line indented by a few spaces. This happens
particularly with the rip register when the address is decoded to a long
function name. Previously, the parsed register did not contain a cooked
register value, and the address on the contunation line was mis-parsed as
a register name. This fixes it.
If GDB cannot print the cooked value of a scalar register on the current
line, it places is on the next line indented by a few spaces. This happens
particularly with the rip register when the address is decoded to a long
function name. Previously, the parsed register did not contain a cooked
register value, and the address on the contunation line was mis-parsed as
a register name. This fixes it.
| kdbg/gdbdriver.cpp | diffblobblamehistory |