![]() ![]() ![]() This error occurs because in the new version Cppcheck (2.12.0) is in the last line write how many checkers was activated after a run (Like: Active checkers: 107/565) and C/C++ Advanced Lint does not yet know how to parse this correctly.įor hot fix it need to add flag in c_cpp_properties. Stacktrace: Error: Line could not be parsed: Active checkers: 107/565 (use -checkers-report= to see details) at /Users/ingram/.vscode/extensions/jbenden.c-cpp-flylint-1.13.1/server/out/server.js:2:12689 at Array.forEach () at a.parseLines (/Users/ingram/.vscode/extensions/jbenden.c-cpp-flylint-1.13.1/server/out/server.js:2:12438) at a.lint (/Users/ingram/.vscode/extensions/jbenden.c-cpp-flylint-1.13.1/server/out/server.js:2:12341) at /Users/ingram/.vscode/extensions/jbenden.c-cpp-flylint-1.13.1/server/out/server.js:2:21825 at Array.forEach () at Function.B (/Users/ingram/.vscode/extensions/jbenden.c-cpp-flylint-1.13.1/server/out/server.js:2:21800) The goal is to detect only real errors in the code, and generate as few false positives (wrongly reported warnings) as possible. It provides unique code analysis to detect bugs and focuses on detecting undefined behaviour and dangerous coding constructs. Please analyze the 'C/C++ FlyLint' Output console. Introduction Cppcheck is an analysis tool for C/C++ code. 'Line could not be parsed: Active checkers: 107/565 (use -checkers-report= to see details)' while validating: /Users/ingram/kohi/engine/src/core/test.c. I tried to use the C/C++ Advanced Lint with Cppcheck-2.12.0 and got an error: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |