Jiyoun

Do I need a separate option when running in cmd line to see the results like the example you gave? I'd really appreciate it if you could give me an answer.

Do I need a separate option when running in cmd line to see the results like the example you gave?

After the previous question, I found that SingleExecutor::check() leads to CppCheck::anyseWholeProgram(), which goes to the virtual pool annalyseWholeProgram at check.h. So I figured out that it was executing the lib/check*.cpp you left an answer for, but from the contents of the getErrorPath function(ex. in CheckNullPointer::analyseWholeProgram), it seemed to save the error path as a variable after already detecting the error. This isn't actual error detection, is it? Or is there something I got...

Hello! I am a student who wants to study static analysis methods. So I downloaded the source code of cppcheck version 2.15.0 and tried to study the flow or method of detecting vulnerabilities. But I am having difficulties, so I am asking for advice or help. I followed the operation of cppcheck based on the cli, and discovered that CppCheckExecutor::check is executed first from main. Here, I understood that the path or options are set with fillSettingsFromArgs, getFiles, and getFileSettings, and then...