Re:CWE Top Most Dangerous Software Weaknesses
by deadletters on Thursday July 13, 2023 @09:24AM
(#36708735)
ASan is better for finding memory corruption afaik
[ Parent
| on HN ]
Re:CWE Top Most Dangerous Software Weaknesses
by amelius on Thursday July 13, 2023 @12:33PM
(#36711937)
Ok. But I'm guessing it has the same problems. I.e., if half your libraries/modules have never seen it, then you'll get a lot of noise. Happy to be proved wrong.
Re:CWE Top Most Dangerous Software Weaknesses
by deadletters on Thursday July 20, 2023 @11:33AM
(#36802030)
The compiler can't add checks into code it hasn't compiled. External modules, unless they are doing weird things which you do want to know about, should not generate ASan reports... on Linux.
Re:CWE Top Most Dangerous Software Weaknesses
by TheNewAndy on Thursday July 13, 2023 @07:06PM
(#36717305)
I use valgrind regularly, and prefer it over asan. asan will result in a faster executable which is nice, but I far prefer valgrind's output than asan's (this might be preference, but I find it to be clearer), and various things break when building with asan so I never make it default. Being able to valgrind stuff without recompiling is very convenient.
I'm also not sure if asan has an equivalent to --leak-check=full