AddressSanitizer reports container overflow during benchmarking about catch2

[horenmar]

Did you compile Catch2 library with ASAN (and container overflow? I am not sure if it is compiled in by default, or needs to be turned on explicitly)?

ContainerOverflow check requires cooperation from the container, which in turn means that all TUs touching std::vector have to have it enabled.

[jonstewart]

TIL! I'm surprised I haven't run into this in the past — but I'm working on a new system, so some things are different. I did not build Catch2 with asan. There are no other asan issues if I turn this detection off.

Given the intrusive nature of container-overflow, has there been consideration of bringing back header-only usage? Having to rebuild Catch2 with different compiler options to suit the situation seems unsustainable.

Regardless, though, thank you for the quick reply and for Catch2 generally! I wrote my own unit test library because GTest/Boost Test/CppUnit were all terrible, but Catch2 has the right ergonomics and I've been able to abandon my own library.

[horenmar]

You can drop the amalgamated .cpp file into your project if you want and it will be compiled as part of your main project build. You can find it in extras/. However, if you have any C++ dependencies, you have to handle propagating compiler flags to your dependencies either way, as there are various ways to break ABI compatibility between them.