Displaying 3 results from an estimated 3 matches for "56ee5ee2".
2012 Jun 18
0
[LLVMdev] MemorySanitizer, a tool that finds uninitialized reads and more
On Mon, Jun 18, 2012 at 02:39:34PM +0400, Kostya Serebryany wrote:
> Another difference from Memcheck is that we propose to use 8 shadow bits
> per byte of application memory and use a
> direct shadow mapping (for 64-bit linux that is just clearing 46-th bit of
> the application memory address).
> This greatly simplifies the instrumentation code and avoids races on shadow
>
2012 Jun 18
2
[LLVMdev] MemorySanitizer, a tool that finds uninitialized reads and more
...> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120618/56ee5ee2/attachment.html>
2012 Jun 18
4
[LLVMdev] MemorySanitizer, a tool that finds uninitialized reads and more
Hello llvmdev,
I would like to propose and discuss yet another dynamic tool, which we call
MemorySanitizer (msan).
The main goal of the tool is to detect uses of uninitialized memory (the
major feature of Valgrind/Memcheck not covered by AddressSanitizer).
It will also find use-after-destruction-but-before-free in C++.
The algorithm of the tool is similar to that of Memcheck (