Hello.
The main problem with 32-bit leak checking is that too many random 4-byte
sequences look like pointers.
In order to find live objects in the heap LSan scans the memory that's
already known to be live and looks for pointers in it. Because LSan doesn't
know anything about data types, it has t
Status: Accepted
Owner: konstant...@gmail.com
CC: euge...@google.com, ramosian.gli...@gmail.com
Labels: Type-Defect Priority-Medium
New issue 358 by euge...@google.com: A number of ASan tests fail in UAR mode
https://code.google.com/p/address-sanitizer/issues/detail?id=358
Do we support running
