Displaying 2 results from an estimated 2 matches for "shadow_byt".
Did you mean:
shadow_byte
2012 Sep 26
1
[LLVMdev] Modifying address-sanitizer to prevent threads from sharing memory
...d be used to modify the
instrumentation's granularity, whether to assume memory blocks are
allocated in multiples of 8, giving less code-blowup. The shadow bytes
would essentially be booleans then. Though this isn't directly related
to the changes I'd require doing.
=== Heap part ===
shadow_byte k: 0 0 0 0 0 0 0 0
<short_id><shadow>
short-id part: 0: main thread
1-30: plugin/thread short-ids
31 = 0x1F, all bits set: unallocated
shadow part: 0-7, same encoding as original.
== Original instrumentation code (ASan USENIX2012 paper)...
2012 Sep 26
0
[LLVMdev] Modifying address-sanitizer to prevent threads from sharing memory
...on's granularity, whether to assume memory blocks are
> allocated in multiples of 8, giving less code-blowup. The shadow bytes
> would essentially be booleans then. Though this isn't directly related
> to the changes I'd require doing.
>
>
> === Heap part ===
>
> shadow_byte k: 0 0 0 0 0 0 0 0
> <short_id><shadow>
>
> short-id part: 0: main thread
> 1-30: plugin/thread short-ids
> 31 = 0x1F, all bits set: unallocated
>
> shadow part: 0-7, same encoding as original.
>
>
> == Original...