[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kdevelop] [Bug 358853] New: include not found in a header causes random parsing/highlighting/code c
From:       David Nolden via KDE Bugzilla <bugzilla_noreply () kde ! org>
Date:       2016-02-01 1:33:06
Message-ID: bug-358853-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

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

            Bug ID: 358853
           Summary: include not found in a header causes random
                    parsing/highlighting/code completion glitches
           Product: kdevelop
           Version: git master
          Platform: unspecified
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: Language Support: CPP (Clang-based)
          Assignee: kdevelop-bugs-null@kde.org
          Reporter: david.nolden.kde@art-master.de

When an include is not found (even if it's not needed at all), then the
semantic analysis, highlighting, code completion, etc. becomes seriously
broken. It seems that clang internally just stops processing the
translation-unit at some point and leaves it half-processed.

Ideally this would be fixed in clang so that such situations are handled more
gracefully. But before that, given how serious the implications are, KDevelop's
problem reporter should at least show an error, pointing out the problem.
Currently, when the #include was missing in a recursively included header, then
the problem-reporter stays completely empty, leaving the user cluelessly with a
half-processed document.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]