| Message ID | 50AA7E29.9060808@net-b.de |
|---|---|
| State | New |
| Headers | show |
On Mon, Nov 19, 2012 at 10:44 PM, Tobias Burnus <burnus@net-b.de> wrote: > Dear all, > > attached is a first draft for -faddress-sanitizer in the release notes. > > I am aware that some changes are imminent,* but I want make a start. > Comments? stack overflow is something different, I guess we want to say "stack buffer overflow". I typically write something like "heap-, stack-, and global- buffer overflow as well as use-after-free bugs". I also suggest adding "use -O1 or higher for better performance" because otherwise "fast memory error detector" is not really true. > > Tobias > > * For instance: > - PowerPC/PowerPC64 Linux support > - Renaming to -fsanitizer=address -fsanitize=address (no 'r') Thanks! > - Addition of -fsanitizer=thread > - libsanitizer builds with sparc (but ASAN_SHADOW_SHIFT is missing?) > - Darwin nearly works?
Index: changes.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v retrieving revision 1.58 diff -p -u -r1.58 changes.html --- changes.html 19 Nov 2012 15:23:15 -0000 1.58 +++ changes.html 19 Nov 2012 18:34:22 -0000 @@ -101,6 +101,13 @@ by this change.</p> inlining decisions (for example in the case of Fortran array descriptors) and devirtualization.</li> </ul></li> + <li><a href="http://code.google.com/p/address-sanitizer/">AddressSanitizer + </a>, a fast memory error detector, has been added and can be + enabled via <code>-faddress-sanitizer</code>. Memory access + instructions will be instrumented to detect out-of-bounds, + use-after-free, stack overflow and global overflow bugs. To get + nicer stacktraces, use <code>-fno-omit-frame-pointer</code>. The + AddressSanitizer is available on IA-32/x86-64/x32 Linux.</li> </ul>