Bug 385803 - parser often leaves echos of previous syntax errors
Summary: parser often leaves echos of previous syntax errors
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: Language Support: CPP (Clang-based) (other bugs)
Version First Reported In: 5.1.80
Platform: Compiled Sources All
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-16 08:49 UTC by RJVB
Modified: 2022-12-10 05:15 UTC (History)
0 users

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


Attachments
snapshot showing error echos (86.39 KB, image/png)
2017-10-16 08:49 UTC, RJVB
Details

Note You need to log in before you can comment on or make changes to this bug.
Description RJVB 2017-10-16 08:49:27 UTC
Created attachment 108372 [details]
snapshot showing error echos

Echos of previous errors often remain after correcting them and waiting for the re-parse to finish. They may be of a slightly different hue.

Sadly I've never been able to link it to any situation in particular, but it may have to do with errors originating in a different file. For instance:

- renaming a headerfile (hard to do that in a way that the parser does not try to load an inexistant file)
- rename a symbol in a .cpp first and only afterwards in the headerfile (or maybe it's the opposite).

That's exactly what I had been doing in the situation shown in the screenshot:
- renamed the class using Find/Replace in Files
- I renamed the files themselves.

Additional observation: the parser claimed it couldn't find qthelpexternalassistant.h; I had to remove and re-enter the #include statement to make it realise the file did exist. This happened in both files including the header.
Comment 1 Justin Zobel 2022-11-10 08:52:17 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-11-25 05:18:45 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-10 05:15:41 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!