https://bugs.kde.org/show_bug.cgi?id=393808
Bug ID: 393808
Summary: Breakpoints are sometimes set using a path that
confuses GDB (and potentially other tools?)
Product: kdevelop
Version: 5.2.1
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: kdevelop-bugs-n...@kde.org
Reporter: mmacl...@webmail.co.za
Target Milestone: ---
Today I ran into a situation where no breakpoints were working inside kdevelop,
breakpoints all just said "pending" even though gdb was otherwise functioning.
After some bother I managed to track this down to my use of a linux "bind
mount"
1) I have a folder "/home/foobar/blah/Development"
2) I have a secondary mount of this folder "/Development"
3) Kdevelop project and all tools etc. use "/Development" everywhere
4) However I accidentally opened my kdevelop project through
"/home/foobar/blah/Development" instead of "/Development"
5) When setting breakpoints kdevelop is passing the path from which the project
was opened to gdb "/home/foobar/blah/Development/src/foo.cpp" instead of
"/Development/src/foo.cpp"
6) This confusingly leaves gdb unable to find the file, even though both paths
are valid (presumably because the paths are hard compiled into the debug
information or similar)
While this is how it presented in this specific case, I do wonder if other
tools may have similar issues - so perhaps (ideally) kdevelop should warn if
the paths inside the project file and the path from which the project are
opened differ from one another.
--
You are receiving this mail because:
You are watching all bug changes.
