Comment #4 on issue 3645 by [email protected]: MSan vs. Serializer:
Fight!
https://code.google.com/p/v8/issues/detail?id=3645
I don't have the report, but as far as I understand, this is what happens.
- A string is allocated [0]. The size of the object is rounded up to
pointer alignment, so when writing the string content after allocation,
there may be padding bytes that are untouched.
- The string is serialized [1]. Notice how the caller only specifies the
end based on the object size, including those padding bytes.
Ideally, we would tell MSAN to allow the serializer to read those padding
bytes without failing.
[0]
https://code.google.com/p/chromium/codesearch#chromium/src/v8/src/heap/heap.cc&q=AllocateRawOneByteString
[1]
https://code.google.com/p/chromium/codesearch#chromium/src/v8/src/serialize.cc&q=OutputRaw&type=cs&sq=package:chromium
--
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
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" 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.
