If your problem is similar to last comment in JENKINS-55350, then we should create a new issue about to handle projects that use different source code encodings.
Ulli Hafner Oh sorry thats right, my issue was regarding the source file encoding. Also I only realized now that C++ files are typically ISO8859-1 encoded and with this settings the source files are parsed just fine.
-I second that, especially for larger C/C++ projects it is difficult to specify an encoding since most newer .cpp / .h files are UTF-8 but older .c Files in the same project are ANSI encoded (We use cppCheck and ClangTidy). The current workaround is to convert all files to UTF-8 just before the analysis.-