search

ramosian-glider / memory-sanitizer

Automatically exported from code.google.com/p/memory-sanitizer
0 stars 0 forks source link

Use-after-dtor thread reporting #90

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
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_Address
Sanitizer), 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.

Original issue reported on code.google.com by nmusgr...@google.com on 4 Aug 2015 at 6:43

GoogleCodeExporter commented 9 years ago 
>> 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.

Original comment by konstant...@gmail.com on 4 Aug 2015 at 6:52