|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Hi Craig,
I read all of the comments several times and I think you misunderstood the behavior of the plugin a lot. Actually it's much simpler than you expect.
Did you consider to use any of these Cppcheck options? I guess they can help you a lot.
--inline-suppr Enable inline suppressions. Use them by placing comments in the form: // cppcheck-suppress memleak before the line to suppress.--suppress=<spec> Suppress a specific warning. The format of <spec> is: [error id]:[filename]:[line]. The [filename] and [line] are optional. [error id] may be * to suppress all warnings (for a specified file or files). [filename] may contain the wildcard characters * or ?. --suppressions-list=<file> Suppress warnings listed in the file. Each suppression is in the format of <spec> above.