Sonni

It seams to work. I had created the .cppcheck project file by hand and it had an error in the <undefine> tag, which explains why I went through all combinations with the undefined flags.</undefine> I made a smalle test aswell: #ifdef A1 int a1=100/0; #ifdef A2 int a2=100/0; #endif #endif #ifdef B1 int b1=100/0; #ifdef B2 int b2=100/0; #endif #endif #ifdef C1 int c1=100/0; #ifdef C2 int c2=100/0; #endif #endif and with different define/undefine's set I get the expected behavior. For the documentation...

When I have defined both -U, -D and --force arguments it looks like cppcheck still performs some og the combinations of defines that are undefined with the -U argument. How does these 3 arguments interact ?

Hi, In a large project I have a macro which CppCheck 2.3 does not know about. The result of this is that CppCheck in this case does not detect a CWE 762 “Mismatching allocation and deallocation” error. Below sample code can reproduce the error. When CWE_762 is undefined no 762 error is reported. If I include the #define or remove the “CWE_762("test");” the error is detected correctly. //#define CWE_762(t) class cwe762test { public: cwe762test() { buffer_ = new char[100]; CWE_762("test"); } cwe762test(const...