Closed abcorrea closed 3 years ago
We are using only -fsanitize=undefined
for now. Experiments did not show any error from this flag. However, it definitely impacted performance (time and memory consumption). It could be useful to temporarily remove this flag to speed up the planner when debugging specific parts of the code.
We would like to use sanitize flags in gcc/clang when compiling the search component. The initial goal is to try them out in the debug compilations.
The first thing to decided is which types of sanitizers we would like to have, given that gcc and clang use different ones. We also might want to look into having two different sets of flags depending on whether we are using clang or gcc.
See: https://lemire.me/blog/2016/04/20/no-more-leaks-with-sanitize-flags-in-gcc-and-clang/ See: https://www.youtube.com/watch?v=MB6NPkB4YVs