https://bugs.kde.org/show_bug.cgi?id=359392
Bug ID: 359392
Summary: Remote debugging does not set file/symbols within gdb.
Product: kdevelop
Version: 4.7.0
Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: NOR
Component: CPP Debugger
Assignee: kdevelop-bugs-n...@kde.org
Reporter: g...@mups.co.uk
CC: niko.s...@gmail.com
When using kdevelop to remote debug via a gdb "Run shell script" and "Run gdb
script", the launched gdb instance does not have any symbols loaded and
breakpoints will not work.
The mouse over help for the "run gdb script" suggests a script like:
shell sleep 5
target remote example.com:1234
continue
However, unless a "file /home/user/path/to/binary_to_run" is added, no symbols
will be loaded.
DebugSession::startProgram when there's no runGdbScript present will use
FileExecAndSymbols however when a runGdbScript is present, this step is
skipped.
Reproducible: Always
I'm not certain if the bug is that when a runGdbScript is present the
FileExecAndSymbols should be handled by kdevelop, or if the UI mouse over needs
to note that you have to set "file /path/to/binary_to_run" for
symbols/breakpoints to work.
If possible it would make more sense for kdevelop to set FileExecAndSymbols as
this would allow the gdbRunScript to remain generic.
Set severity to Minor, as the workaround is use "file" in the gdbRunScript with
the path to the binary you're planning to debug.
--
You are receiving this mail because:
You are watching all bug changes.
