Comment #4 on issue 323 by [email protected]: AddressSanitizer:
double-free with zero-length XHR, depending on behavior of realloc(p, 0)
http://code.google.com/p/address-sanitizer/issues/detail?id=323
The "bug" in ASAN is that its modeling of realloc must be consistent with
that in the actual realloc implementation in use.
http://open-std.org/JTC1/SC22/WG14/www/docs/dr_400.htm
realloc in practice has one of ~three sets of incompatible semantics.
Whatever semantics are modeled now, can't possibly be consistent with all
three semantics.
I have no idea how to ensure ASAN's realloc modeling is compatible with
that in the realloc linked against when compiling. (Or linked against
dynamically, if such a thing is possible, which I don't know that it
is/isn't.)
--
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.
