[RFC] Exception-friendly ASan annotations of std::string

[Ivan Baravy]

Hello,

I'm working on address sanitization of standard containers. The aim is
to detect and report accesses between size and capacity. The issue I
faced is related to std::length_error and std::bad_alloc exceptions. I
can get std::bad_alloc via huge fill insert into std::string. ASan adds
a memory overhead (internal structures) to user allocations and, when
enabled, it intercepts memory-related functions, failed allocations of
vital structures make it terminate the process. Thus it looks like
pointless for ASan annotations to be friendly to std::length_error and
std::bad_alloc exceptions.

So my question is if it's acceptable to not consider std::length_error
and std::bad_alloc in address sanitization design?

Regards,
Ivan