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 to aggressively treat everything that looks like a pointer as such. This approach may lead to false negatives (missing memory leaks), and on 32-bit platforms it actually does.
HTH, Alex On Nov 28, 2014 5:15 AM, "wuning.shi" <wuning....@gmail.com> wrote: > hello > > we want to use lsan on 32 bit arm platform, and i see your explain of the > main problem. > https://code.google.com/p/address-sanitizer/issues/detail?id=294 > > i have read some source code. > but i still can't understand why 64 bit platform has no problem. why lsan > need check a 32bit number? > > can you explain more about lsan design principle please? > > thanks very much : ) > > -- You received this message because you are subscribed to the Google Groups "address-sanitizer" group. To unsubscribe from this group and stop receiving emails from it, send an email to address-sanitizer+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
