Comment #5 on issue 325 by [email protected]: Leak of size 0 reported
as leak of size 1
http://code.google.com/p/address-sanitizer/issues/detail?id=325
What we could do is have the user_requested_size metadata field always
contain the actual requested size (possibly 0), and have two accessors (one
returns user_requested_size for use in reports, the other returns
max(user_requested_size, 1) for internal use). We just need to go through
the code carefully and separate the two use cases.
--
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.
