search

ramosian-glider / memory-sanitizer

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

MSan reports "invalid origin" on use-after-free #29

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
MSan poisons deallocated memory with 0xffffffff origin.

Options:
1. do not poison deallocated memory
2. get a stack trace and build a proper origin label
3. use a magic origin value, common for all deallocations

Original issue reported on code.google.com by euge...@google.com on 16 Sep 2013 at 9:23

GoogleCodeExporter commented 9 years ago 
And in any case the report could redirect users to ASan as a better tool for 
this kind of bugs

Original comment by euge...@google.com on 16 Sep 2013 at 9:24

GoogleCodeExporter commented 9 years ago 
I went with option (2) in r190781.
Running benchmarks now.

Original comment by euge...@google.com on 16 Sep 2013 at 11:17

GoogleCodeExporter commented 9 years ago 
Did not see any significant performance regression on SPEC.

Original comment by euge...@google.com on 10 Oct 2013 at 11:16

GoogleCodeExporter commented 9 years ago 
Adding Project:MemorySanitizer as part of GitHub migration.

Original comment by gli...@google.com on 30 Jul 2015 at 9:22