Jeremy Singy

Hi, With the latest CppCheck 2.5, I have an issue when launching CppCheck on our codebase. This results in a crash (segfault). I could simplify the initial code (quite complicated and spreaded between multiple includes) to this minimal piece: namespace ns { auto var{0}; } namespace ns { auto var2{0}; } When launching with cppcheck --enable=all --std=c++17 test.cpp, I get the segmentation fault. If I put var2 in the same namespace declaration, if I use copy-initialization (with =), or if I remove...

Hi, With the latest CppCheck 2.5, I have an issue when launching CppCheck on our codebase. This results in a crash (segfault). I could simplify the initial code (quite complicated and spreaded between multiple includes) to this minimal piece: namespace ns { auto var{0}; } namespace ns { auto var2{0}; } When launching with cppcheck --enable=all --std=c++17 test.cpp, I get the segmentation fault. If I put var2 in the same namespace declaration, if I use copy-initialization (with =), or if I remove...

Hi, With the latest CppCheck 2.5, I have an issue when launching CppCheck on our codebase. This results in a crash (segfault). I could simplify the initial code (quite complicated and spreaded between multiple includes) to this minimal piece: namespace ns { auto var{0}; } namespace ns { auto var2{0}; } When launching with cppcheck --enable=all --std=c++17 test.cpp, I get the segmentation fault. If I put var2 in the same namespace declaration, if I use copy-initialization (with =), or if I remove...

Hi, With the latest CppCheck 2.5, I have an issue when launching CppCheck on our codebase. This results in a crash (segfault). I could simplify the initial code (quite complicated and spreaded between multiple includes) to this minimal piece: namespace ns { auto var{0}; } namespace ns { auto var2{0}; } When launching with /cppcheck --enable=all --std=c++17 test.cpp, I get the segmentation fault. If I put var2 in the same namespace declaration, if I use copy-initialization (with =), or if I remove...