Issue 90 in memory-sanitizer: Use-after-dtor thread reporting

[memory-s...@googlecode.com]

Status: Accepted
Owner: nmusgr...@google.com
CC: euge...@google.com, k...@google.com
Labels: Type-Defect Priority-Medium ProjectMemorySanitizer

New issue 90 by nmusgr...@google.com: Use-after-dtor thread reporting
https://code.google.com/p/memory-sanitizer/issues/detail?id=90

Current failures are reported with a stack trace to the failure point, with
a process id.

These reports make it difficult to determine exactly which threads are
poisoning and accessing memory.

In order to achieve reporting similar to AddressSanitizer
(https://code.google.com/p/address-sanitizer/wiki/AddressSanitizer#Using_AddressSanitizer),
the runtime callback function to poison memory must know the variable type
(heap, stack, global). If it is on the heap, redzones may be used for
keeping track of thread information.


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

[memory-s...@googlecode.com]

Comment #1 on issue 90 by konstant...@gmail.com: Use-after-dtor thread
reporting
https://code.google.com/p/memory-sanitizer/issues/detail?id=90

>> If it is on the heap, redzones may be used for keeping track of thread
>> information.

Not that simple.
A single heap chunk may contain multiple C++ objects.