Bug 384775 - 5.2 branch: parser issues (and a few other annoyances)
Summary: 5.2 branch: parser issues (and a few other annoyances)
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources macOS
: NOR major
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2017-09-16 17:30 UTC by RJVB
Modified: 2022-12-31 05:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
parser glitch 1 (215.59 KB, image/png)
2017-09-16 17:30 UTC, RJVB
Details
parser glitch 2 (248.63 KB, image/png)
2017-09-16 17:31 UTC, RJVB
Details
parser glitch 3 (235.37 KB, image/png)
2017-09-16 17:32 UTC, RJVB
Details
parsing glitch in another project (165.19 KB, image/png)
2017-09-19 15:10 UTC, RJVB
Details

Note You need to log in before you can comment on or make changes to this bug.
Description RJVB 2017-09-16 17:30:30 UTC
Created attachment 107880 [details]
parser glitch 1

I'm transitioning to the 5.2 branch and must say I'm having a really hard time not bailing out back to the safety of 5.1.2 .

The main issue I'm reporting here is clang parser regression. Where v5.1.2.5 happily parses KDevelop's own code, the current 5.2 branch/head sees many issues as evidenced by the screenshots. It uses libclang 4.0.1, from the compiler I'm using, which builds without issues.

Additionally I notice that
- the problem reporter fails to remember its column width settings
- my project always opens with the Find/Replace in Files toolview open (= yet another toolview visibility restore issue).
Comment 1 RJVB 2017-09-16 17:31:14 UTC
Created attachment 107881 [details]
parser glitch 2
Comment 2 RJVB 2017-09-16 17:32:04 UTC
Created attachment 107882 [details]
parser glitch 3
Comment 3 RJVB 2017-09-16 17:33:05 UTC
Comment on attachment 107880 [details]
parser glitch 1

This glitch doesn't occur on Linux (same build).
Comment 4 RJVB 2017-09-19 15:10:44 UTC
Created attachment 107906 [details]
parsing glitch in another project

So the 5.2 parser has problems not just with the KDevelop tree itself. I'm also seeing issues with the Purpose tree, and as shown here, with a project that has nothing to do with KDevelop/KDevPlatform whatsoever.

Often the initial impression when first opening a document is that all is fine. Then you reparse one way or another, and the glitches pop up.

Could this be related to the closing of resources that were simply left open/active in the 5.1 branch and earlier? IIRC Kevin has been working on that kind of (intended) improvement.
Comment 5 Milian Wolff 2017-09-21 13:05:27 UTC
Can you try again? I think I may just have fixed this issue in the master branch.
Comment 6 Milian Wolff 2017-09-21 13:05:58 UTC
waiting for info, see previous comment
Comment 7 RJVB 2017-09-21 15:05:20 UTC
This was committed to the 5.2 branch too, from the looks of it?

If so I have to disappoint: the reported issues with e.g. cmakeutils.cpp and cmakepreferences.cpp persist. These notable (from a ML post):

- when usins CMake Server import, the parser now only doesn't find the cmakebuilderconfig.h and ui_cmakebuildsettings.h headers in cmakeutils.cpp and cmakepreferences.cpp .

- when using JSON-based import, the parser doesn't find the interfaces/icore.h , KLocalizedString, KMessageBox and KJobWidgets headers in cmakepreferences.cpp and complains about undeclared QString and QStringLiteral in cmakeutils.cpp 

(Turning off cmake server import is trivial using a wrapper script around cmake, a backdoor I really appreciate because it also gives me full control over exactly how cmake is called.)
Comment 8 Andrew Crouthamel 2018-09-28 02:38:27 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 set the bug status 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 9 RJVB 2018-09-28 07:59:52 UTC
This lead to https://phabricator.kde.org/D7930, ultimately, which is still relevant for the 5.3 branch too.
Comment 10 Justin Zobel 2022-12-01 04:34:27 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 11 Bug Janitor Service 2022-12-16 05:13:18 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 12 Bug Janitor Service 2022-12-31 05:23:29 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!