I've noticed there's some errors that seem to be missing from the --errorlist.
- allocaCalled
- stlcstrthrow
- pureVirtualCall
- comparisonOfBoolWithInvalidComparator
- invalidScanfFormatWidth_smaller
- redundantBitwiseOperationInSwitch
- invalidFree
As far as I can tell, all of these are run in their respective runChecks/runSimplifiedChecks methods, but arent in getErrorMessages (or for invalidScanfFormatWidth_smaller, where it only has the case to show invalidScanfFormatWidth), so none of them show up in the errorlist.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for reporting this.
IMHO they were just beeing forgotten.
Instead of "allocaCalled" something more generic like "functionCalled" could maybe be better since it also depends on the library which functions are marked with a warning. I am not sure if it makes sense to list all according functions from the libraries.
There is already a related ticket where amai also added your report: https://trac.cppcheck.net/ticket/7772
Last edit: versat 2018-06-20
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've noticed there's some errors that seem to be missing from the --errorlist.
- allocaCalled
- stlcstrthrow
- pureVirtualCall
- comparisonOfBoolWithInvalidComparator
- invalidScanfFormatWidth_smaller
- redundantBitwiseOperationInSwitch
- invalidFree
As far as I can tell, all of these are run in their respective
runChecks/runSimplifiedChecksmethods, but arent ingetErrorMessages(or forinvalidScanfFormatWidth_smaller, where it only has the case to showinvalidScanfFormatWidth), so none of them show up in the errorlist.Thanks for reporting this.
IMHO they were just beeing forgotten.
Instead of "allocaCalled" something more generic like "functionCalled" could maybe be better since it also depends on the library which functions are marked with a warning. I am not sure if it makes sense to list all according functions from the libraries.
There is already a related ticket where amai also added your report:
https://trac.cppcheck.net/ticket/7772
Last edit: versat 2018-06-20