https://bugs.kde.org/show_bug.cgi?id=431168
--- Comment #5 from insilications ---
https://invent.kde.org/sdk/clazy/-/merge_requests/30
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431168
--- Comment #4 from insilications ---
Created attachment 134561
--> https://bugs.kde.org/attachment.cgi?id=134561&action=edit
Proposed patch
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431168
--- Comment #3 from insilications ---
Created attachment 134560
--> https://bugs.kde.org/attachment.cgi?id=134560&action=edit
Minimal example
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=431168
--- Comment #2 from insilications ---
The proposed patch fixes the issue. DiagnosticMessage indeed received an empty
and invalid file location from a macro location. Checking for a macro location
now allows DiagnosticMessage to receive a proper file
https://bugs.kde.org/show_bug.cgi?id=431168
--- Comment #1 from insilications ---
Analyzing "/insilications/apps/test/test/main.cpp" [Clazy].
Failed to analyze "/insilications/apps/test/test/main.cpp": Clazy crashed.
Command line: /usr/bin/clazy-standalone -checks=qproperty-t
34559
--> https://bugs.kde.org/attachment.cgi?id=134559&action=edit
Minimal example
Minimal example attached
01:59:44: Starting: "/usr/bin/qmake" /insilications/apps/test/test/test.pro
-spec linux-g++ CONFIG+=debug CONFIG-=qml_debug
01:59:44: Starting: "/usr/bin/make"
