When I scan a repository of hundreds of C files (Version: V2.15.0 linux)
Based on the output log, I found that: 1. At the beginning, the scanning speed is very fast, but after a period of time, the speed of log printing will be much slower 2. Each cppcheck process will occupy 700M of memory
I really want to know why this situation occurs and where the configuration is wrong? Especially why does it occupy such a high amount of memory, and how can I avoid it?
Here is the command I ran:
./cppcheck -j 8 --force --max-configs=1000 --xml --xml-version=2 ./ source_code/ 2>./report/report.xml
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1. According to the information printed in the log, it is still similar to before:
The scanning of the first few hundred files seems to be completed quickly, but it is getting slower and slower, taking several minutes to scan a file
When I scan a repository of hundreds of C files (Version: V2.15.0 linux)
Based on the output log, I found that:
1. At the beginning, the scanning speed is very fast, but after a period of time, the speed of log printing will be much slower
2. Each cppcheck process will occupy 700M of memory
I really want to know why this situation occurs and where the configuration is wrong? Especially why does it occupy such a high amount of memory, and how can I avoid it?
Here is the command I ran:
./cppcheck -j 8 --force --max-configs=1000 --xml --xml-version=2 ./ source_code/ 2>./report/report.xml
Does adding a build cache with --cppcheck-build-dir=
Firstly, thank you for your reply
As you said, I added:-- cppcheck-build-dir=./
1. According to the information printed in the log, it is still similar to before:
The scanning of the first few hundred files seems to be completed quickly, but it is getting slower and slower, taking several minutes to scan a file
2. Each cppcheck process occupies 700M of memory
Last edit: 石增辉 2024-12-19