Mon Mar 22, 2021 7:15 am
I cannot express my frustration enough with KDevelop's community. It seems like no matter where I try to find help, no one is there. The IRC channel is dead and my bug reports from 2 years ago have gone unanswered.
How do I open projects? Project -> Open/Import no longer works.
Why does F4 (jump to first error) stop working after debugging?
Bug report: https://bugs.kde.org/show_bug.cgi?id=395441
Why does the variable tab break when the address changes?
Bug report: https://bugs.kde.org/show_bug.cgi?id=395438
Can I PLEASE get SOMEONE to tell me what is going on and when ANY of this will be fixed?
The F4 and debug bugs have been in KDevelop for longer than 5 years and no one cares? How can I be the only person who has found this?
Wed Mar 24, 2021 11:13 pm
This actually works for me on 5.6.1 (AppImage) and 5.6.40. Its weird that you don't see any files even with filter set to "All Files". Not being able to open a project would be so glaring bug, that I doubt KDE devs would overlooked it. Could it be something Gentoo specific?
This really does not work even on 5.6.40. Not just after the debugging. If you just "Execute current launch", then F4 will stop working for the next build. If the user switches away from "Build" tool view to different one, and then back to "Build" tool view and then it will start work again. This looks like something easy to fix maybe I will take a look at it.
The issue is in using the pointers. The debugger cannot really explore a whole structure if you provide just a the pointer pointing on it - because pointer is just a initial address of the struct. If you are watching a pointer you need to tell the debugger how the pointed data should be actually interpreted. So to watch your bar variable you need to add into "Variable" toolview:
In that case member variables of the bar struct will be always accessible. I agree that the behavior of the watch should not depend on whether the user expands some TreeView. Thats confusing and should be fixed, but its not a killer bug. Most of the other IDEs would just show you the value of the 1 byte pointed by the pointer in similar case.