Bug 389550

Summary:	C/C++ language support sometimes fail to resolve included files when include file itself has never been included.
Product:	[Applications] kdevelop	Reporter:	Venca B Spam <vbspam>
Component:	Language Support: CPP (Clang-based)	Assignee:	kdevelop-bugs-null
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version First Reported In:	5.2.1
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	Video of LanguageSupportFailingScenario1 Sample project of LanguageSupportFailingScenario1

Description Venca B Spam 2018-01-28 11:49:16 UTC

C/C++ language support sometimes fail to resolve include files when include file itself has never been included.

* How to reproduce? *

1. Download attached sample test case project
2. Follow steps on the video bug report attached. Shortly:
 - Start fresh new KDevelop session
 - Open the project attached and let the background parser finish its job
 - Open the include file "Bar/Bar.hpp"
 - Observe the line with "Thirdparty/Interface.hpp" inclusion

* What happens? *

Although the #include directive is correct in the context of the build system, KDevelop marks the line as not only problem (which is incorrect) it also do not use the "Thirdparty/Interface.hpp" for further language analyse.

* What is expected? *

Even if the include file is not actually never included, it should be properly parsed. KDevelop should not generate confusing false error positives.

* Observation *

When the include file "Bar/Bar.hpp" is included in another file (e.g. Foo.cpp), the problem disappears (demonstrated on the video attached).

Also later when is such inclusion removed (from Foo.cpp) the problem does not reappear.

Comment 1 Venca B Spam 2018-01-28 11:52:40 UTC

Created attachment 110178 [details]
Video of LanguageSupportFailingScenario1

Added video of LanguageSupportFailingScenario1.

Comment 2 Venca B Spam 2018-01-28 11:55:01 UTC

Created attachment 110179 [details]
Sample project of LanguageSupportFailingScenario1

Added sample project of LanguageSupportFailingScenario1.

Comment 3 Venca B Spam 2018-01-28 12:00:29 UTC

The underlying cause of this issue may be related to the issue I already reported here https://bugs.kde.org/show_bug.cgi?id=387272 .

Comment 4 Justin Zobel 2022-11-15 22:58:53 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 5 Bug Janitor Service 2022-11-30 05:14:57 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 6 Bug Janitor Service 2022-12-15 05:15:03 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!