|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi, this looks more like issue of Cppcheck tool itself and not Cppcheck Plugin. The tool outputs a XML file and specifies encoding="UTF-8" so it is responsible for the content to be indeed utf-8. The plugin loads the file header, sees utf-8 encoding and tries to load the file with it. But there is probably a broken byte sequence that can't occur in utf-8 so it will throw MalformedByteSequenceException exception.
If you use --enable=style or --enable=all, the tool will probably find more issues and one of the additional one contains the broken character. Can you attach your report to be able to verify this theory, please?
I have just tried to generate all possible issue types that can occur in the output but the plugin read the report successfully. I used Cppcheck 1.61 and 1.63 (the latest one), plugin 1.15-SNAPSHOT, Debian GNU/Linux.