https://bugs.kde.org/show_bug.cgi?id=387391
--- Comment #7 from Venca B Spam <vbs...@centrum.cz> --- Ok, I did the test and it looks even weirdest then before. I also enabled the KDEV_CLANG_DISPLAY_ARGS=1 to see how the Clang is being invoked. Observations: a) 'sometimes' it is invoked without proper -I include definitions which produces the expected issue described here. b) 'sometimes' it is invoked WITH proper -I which gives proper output just with some linking issues (I assume it does not break the think) c) however 'sometimes' even it was initially OK (see the bullet b) above), when I press e.g. " " (space) in the editor, the editor changes the hint/parsing to error. What is really weird here is, that I do not see any Clang invocation nor even attempt to run Clang (at the moment I pressed the keyboard " " - could be any character triggering the dirty save flag) Summary: - The change to from ok to an error state changes without Clang invocation - It may start with an error state on the beginning based on Clang output which correctly generate the error as it do not get proper -I includes on argument line. Is there any debug environment variables I can use to enable logs to observe the parser loop/events? -- You are receiving this mail because: You are watching all bug changes.
