We must make the access of 'push_back' dependent, too. Otherwise, name
lookup does not find the name. Earlier compilers were more permissive and
did find the name.
(cherry picked from upstream commit 5f55847d441aba7742417e78c3b4fbe8344acc5e)
(cherry picked from commit a6469516e6)
Since gdb 7.1, the address does not start at the beginning of a line, and
it can be prefixed by a pointer => that indicates the current instruction.
(cherry picked from upstream commit 5c5f34852d30337ef7c23ef4e88d50ecee1c0703)
(cherry picked from commit 26a2a75988)
When a string ends in an incomplete multi-byte sequence, gdb adds an
<incomplete sequence...> fragment to the end of the string. Previously,
this resulted in a parse error and incomplete variable information.
Reported by Kevin Lemay.
(cherry picked from upstream commit 03da8a5ec97c8c7b125b2bd453d2f1c3a018d477)
(cherry picked from commit a8abc77457)
The syntax of the 'disassemble' command changed in gdb 7.1: it now requires
a comma between the two address expressions. Previously, KDbg showed an
error message instead of assembler code when a plus in front of a source
code line was clicked.
Reported by Gerfried Essler.
This reverts part of the previous commit.
(cherry picked from upstream commit b6ee6a035abe41f7c0d59fbd830e895b6edeb748)
(cherry picked from commit a57f5f7c68)
Cherry picked and adapted from commit 0efc808f from the original author
of kdbg, code available at https://github.com/j6t/kdbg under GPL 2.0"
Quote from the author:
In early days of KDbg, it was important to use a suitable command to load
a core file. This was before gdb 4.16. To pick the right command, the
version number was parsed from gdb's greeting.
At least with modern gdb the regular expression does not match anymore.
So let's assume that nobody is using ancient gdb anymore, and always use
the modern command.
Signed-off-by: gregory guy <g-gregory@gmx.fr>
(cherry picked from commit 50d3d7881e)
Johannes Sixt
gregory guy