Status: Accepted
Owner: [email protected]
CC: [email protected]
Labels: Type-Enhancement Priority-Low
New issue 304 by [email protected]: make unaligned pointers handling in
LSan more useful
http://code.google.com/p/address-sanitizer/issues/detail?id=304
With use_unaligned=1, LSan will consider unaligned byte patterns as
pointers. This matters in certain rare cases, e.g. when pointers are stored
in a packed struct. To help detect such cases, HeapChecker supports a mode
where we run two leak checks back-to-back, one of which takes into account
only aligned byte patters and the other considers all byte patters. By
comparing the results, HeapChecker can detect the presence of unaligned
pointers. (The idea being that this is more convenient than running the
program twice with use_unaligned=1/0 and comparing the results manually.)
LSan could support a similar feature with a relatively simple change,
although the utility of this is unclear. False positives due to unaligned
pointers are quite rare (only 2 cases in the first year of LSan deployment)
and it seems that the minor convenience boost might not be worth the
complexity increase.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
