I have been unable to reduce these two bugs to a minimal code example. They only show up when run against the entire directory
This is the project https://github.com/Hamlib/Hamlib/
There is a cppcheck.sh script which takes no arguments that produces the following two problem....first one is the ternary operator apparently doesn't know how to recurse.
2nd problem is errors without a -1 line number.
I have been unable to reduce these two bugs to a minimal code example. They only show up when run against the entire directory
This is the project
https://github.com/Hamlib/Hamlib/
There is a cppcheck.sh script which takes no arguments that produces the following two problem....first one is the ternary operator apparently doesn't know how to recurse.
2nd problem is errors without a -1 line number.
oot@mdblack-VirtualBox:/home/mdblack/src/hamlib# more cppcheck.log
rigs/yaesu/ft3000.c:117:10: error: AST broken, ternary operator missing operand(
s) [internalAstError]
[LVL_RAWSTR] = { .min = { .i = 0 }, .max = { .i = 255 } },
^
rigs/yaesu/ftdx101.c:105:10: error: AST broken, ternary operator missing operand
(s) [internalAstError]
[LVL_RAWSTR] = { .min = { .i = 0 }, .max = { .i = 255 } },
^
tests/ampctl.c👎0: information: Unmatched suppression: knownConditionTrueFalse [unmatchedSuppression]
^
tests/ampctl_parse.c👎0: information: Unmatched suppression: knownConditionTrueFalse [unmatchedSuppression]
^
tests/rigctl.c👎0: information: Unmatched suppression: knownConditionTrueFalse
[unmatchedSuppression]
^
tests/rigctl_parse.c👎0: information: Unmatched suppression: knownConditionTrueFalse [unmatchedSuppression]
^
tests/rotctl_parse.c👎0: information: Unmatched suppression: knownConditionTrueFalse [unmatchedSuppression]