The changes from e89c041 as part of
SERVER-45884 disabled running the hang analyzer on ASan build variant (i.e. builders using --sanitize=address) via assert.soon() due to gcore not respecting the madvise() settings on the 20TB of shadow memory. This had come up previously in SERVER-29886 for the "timeout" phase in the etc/evergreen.yml project configuration and was resolved by running hang_analyzer.py without the -c option in order to avoid producing core dumps.
We could similarly have the mongo shell omit the
c option when running hang_analyzer.py. On a related note - the mongo shell offers an _isAddressSanitizerActive() function which returns true if it was compiled with -sanitize=address (we generally assume the server binaries have the same build flags), so we should consider removing TestData.isAsanBuild to avoid there being two ways of expressing the same thing.
Add a test to check that the hang_analyzer still runs on ASan without dumping core.