https://bugs.kde.org/show_bug.cgi?id=379317

            Bug ID: 379317
           Summary: Clang parser issues
           Product: kdevelop
           Version: 5.1.0
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Language Support: CPP (Clang-based)
          Assignee: kdevelop-bugs-n...@kde.org
          Reporter: tedfed...@gmail.com
  Target Milestone: ---

In upgrading from Kdevelop 5.0.3 to 5.1.0 I find there are some new issues with
the Clang parser.  
I finally figured out in 5.0.3 that when I wasn't getting parsing in a file
that needed to look in the "Problems" tab which would show me which include
files that were not found.  Once I resolved the issue with the include files
then the parsing would work.

5.1.0 appears to take much longer to try to parse the file and then does not
appear to list unresolved paths to include files as "Problems".  And also
doesn't always flag the include file as an issue (In 5.0.3 there would be a red
tilda mark to indicate an issue with the include file). It could be if I waited
long enough then 5.1.0 would eventually tag the problem include files.  The
parser though seems to get stuck and never shows me the issues.  I have to go
through the include files one-by-one to figure out which is a problem.  Once I
finally get this right then the parse works, but again it is slower than in
5.0.3.

I would just go back to 5.0.3, but I found that in the 5.0.3 the modification
times on my files would mysteriously change just by opening Kdevelop even
though I had not changed the file or even had that particular file open in the
editor.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to