Per Arnold Blaasmo

Due to lines 1346-1347 in cppcheck.cpp: if (addon != "misra" && !addonInfo.ctu && endsWith(files.back(), ".ctu-info")) continue; Running cppcheck with the option --addon=misra vs --addon=misra.py yields different results. They should not. The example in the manual used the option --addon=misra.py. What is the prefered way to call and addon? Per A. PS! simple example: Using 'misra' give 2 violations, using 'misra.py' gives 1 violation $: ~ /tmp/misra-test> cppcheck --addon=misra interrupts.c Checking...

Due to lines 146-1347 in cppcheck.cpp: if (addon != "misra" && !addonInfo.ctu && endsWith(files.back(), ".ctu-info")) continue; Running cppcheck with the option --addon=misra vs --addon=misra.py yields different results. They should not. The example in the manual used the option --addon=misra.py. What is the prefered way to call and addon? Per A. PS! simple example: Using 'misra' give 2 violations, using 'misra.py' gives 1 violation $: ~ /tmp/misra-test> cppcheck --addon=misra interrupts.c Checking...