Bug 393808 - Breakpoints are sometimes set using a path that confuses GDB (and potentially other tools?)
Summary: Breakpoints are sometimes set using a path that confuses GDB (and potentially...
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 5.2.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-03 15:51 UTC by malcolm macleod
Modified: 2022-12-21 05:20 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description malcolm macleod 2018-05-03 15:51:12 UTC
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.
Comment 1 Justin Zobel 2022-11-21 08:21:47 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-12-06 05:17:40 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-12-21 05:20:06 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!