New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 901852 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Nov 15
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Document meaning of 0xBE in ASAN docs better

Project Member Reported by metzman@chromium.org, Nov 5

Issue description

As 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.

 
Description: Show this description
Cc: brucedaw...@chromium.org
Owner: metzman@chromium.org
Status: Assigned (was: Untriaged)
Labels: Pri-2
Cc: kcc@chromium.org euge...@chromium.org
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!


done, thanks!
Status: Verified (was: Assigned)
Thanks Kostya!

Sign in to add a comment