https://bugs.kde.org/show_bug.cgi?id=402992
Bug ID: 402992
Summary: circular symlinks can lock up kdevelop
Product: kdevelop
Version: 5.3.1
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
Projects with circular symlinks can send KDevelop down the rabbit hole...
This looks like a duplicate of #258920 but that one is so old I preferred to
file a new issue.
STEPS TO REPRODUCE
1. get the libacl source code (master branch from my fork github:RJVB/acl)
2. autogen.sh && configure
3. create a KDevelop project from the resulting Makefile
4. close the session
5. reopen the session
6. start editing and (re)building the project
OBSERVED RESULT
Step 3 probably succeeds (it did for me) but steps 5 or 6 are very likely to
lead to a freeze.
EXPECTED RESULT
Normal operation
SOFTWARE/OS VERSIONS
Linux 4.14.23, KF5 5.52.0
Qt Version: 5.9.7
ADDITIONAL INFORMATION
The culprits here are 2 symlinks put in place by the project's configure
script:
include/acl -> /path/to/aclSrc/include
include/sys -> /path/to/aclSrc/include
The backtrace is huge when locked so I have little idea what is really going
wrong here except that most of the backtraces I've seen seem to implicate the
git plugin which "does something, for some reason" each time a change is
detected in the project tree.
--
You are receiving this mail because:
You are watching all bug changes.
