Trying to analyse a large project with MISRA always results in crashing misra.py. I've broken down the problem onto very small project, see attached zip-file.
Reason seems to be that*.ctu-info files provided by "cppcheck-addon-ctu-file-list" should be read but wasn't generated.
1. First case is when non-ASCII characters are inside the code (see Test2.c): in this case "Test2.c.ctu-info" isn't generated and misra.py crashes on trying to read it
2. Second case is when using --cppcheck-build-dir: misra.py wants to read "Test3.c.analyzerinfo.ctu-info" but (empty!) "Test3.a1.ctu-info" was generated instead (regardless whether there ar non-ASCIs or not!)
See also some comments in attached CppCheck.bat.
Note that CppCheck V.2.7 works fine!
Hi Everyone,
Trying to analyse a large project with MISRA always results in crashing misra.py. I've broken down the problem onto very small project, see attached zip-file.
Reason seems to be that*.ctu-info files provided by "cppcheck-addon-ctu-file-list" should be read but wasn't generated.
1. First case is when non-ASCII characters are inside the code (see Test2.c): in this case "Test2.c.ctu-info" isn't generated and misra.py crashes on trying to read it
2. Second case is when using --cppcheck-build-dir: misra.py wants to read "Test3.c.analyzerinfo.ctu-info" but (empty!) "Test3.a1.ctu-info" was generated instead (regardless whether there ar non-ASCIs or not!)
See also some comments in attached CppCheck.bat.
Note that CppCheck V.2.7 works fine!
Regards from Meerbusch
Thomas
Hi sorry this answer may be late but in my case on Cppcheck v2.6 and v2.8 I had to modify misra.py and after :
I add these lines to rename CTU files :
This seems to fix your point 2.
Hi Julien,
thanks for figuring out a workaround. But in newer Versions (since 2.9) all seems to work fine again.
Regards from Meerbusch
Thomas