Document meaning of 0xBE in ASAN docs better |
|||||
Issue descriptionAs requested by brucedawson@ in crbug.com/897872#c34 In the documentation of 0xBE it should also be listed as 0xBEBEBEBE or as the 64-bit value because searching for BE leads to too many false hits.
,
Nov 5
,
Nov 5
,
Nov 15
Evengii or Kostya: I've gotten feedback from Bruce that it is unclear when one is looking at an allocated-but-unitialized value under ASAN. What do you think of adding bullet to the FAQ on https://github.com/google/sanitizers/wiki/AddressSanitizer : * Q: What do 0xbebebebebebebebe and 0xbebebebe mean? * A: ASan, by default, writes 0xbe to newly allocated memory (see [malloc_fill_byte](https://github.com/google/sanitizers/wiki/AddressSanitizerFlags#run-time-flags)). 0xbebebebebebebebe is (possibly) a 64-bit value that was allocated but not initialized while 0xbebebebe is (possibly) a 32-bit value that was allocated but not initialized. I would do a pull request, but I don't think this is possible for GitHub wiki pages, sorry!
,
Nov 15
done, thanks!
,
Nov 15
Thanks Kostya! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by metzman@chromium.org
, Nov 5