Refer https://github.com/google/sanitizers/wiki/AddressSanitizer for details.

Attention: You should enable the address sanitizer in all CAPS components or in none of it. Else confusing error messages might happen at run-time. It still works if the address sanitizer is enabled for some CAPS components only. But it needs some tweaks to make them run again.

You might see an error like this:

==39148==ASan runtime does not come first in initial library list; you should
  either link runtime to your application or manually preload it with LD_PRELOAD.

One explanation is, the executable you want to run isn't ASAN enabled, but some or all other components (libraries) it uses are.

To make it run again, you can set:

ASAN_OPTIONS=verify_asan_link_order=0

But in this case ASAN might interfere with other libraries and does not work as expected. Take a closer look into the /etc/ld.so.preload what kind of other libraries (maybe) are loaded first.

A more robust solution is from the website mentioned above: Run the executable with an

LD_PRELOAD=path/to/asan/runtime/lib

to ensure ASAN is the first library in the list.

Note: Keep in mind if only some parts of the whole process are ASAN enabled, the result of its checks might be confusing due to false positives.