[Bug 6038] New: Add support for GCC 4.8's -fsanitizer for Debug Configurations

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=6038

           Summary: Add support for GCC 4.8's -fsanitizer for Debug
                    Configurations
           Product: uClibc
           Version: 0.9.33.3
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Other
        AssignedTo: unassigned at uclibc.org
        ReportedBy: noloader at gmail.com
                CC: uclibc-cvs at uclibc.org
   Estimated Hours: 0.0


GCC 4.8 introduced two helpful features for debugging and diagnostics. First is
a memory sanitizer, and second is a thread sanitizer. Memory saniter acts a lot
like dmalloc or Valgrind and is invoked with -fsanitizer=memory. Thread
sanitizer is a lot like Helgrind is invoked with -fsanitizer=thread.

There are numerous benefits to finding memory and threading problems early in
the development process, and not letting the errors creep into production
(libupnp is a perfect example).

References: http://gcc.gnu.org/gcc-4.8/changes.html,
https://code.google.com/p/address-sanitizer/,
https://code.google.com/p/data-race-test/wiki/ThreadSanitizer, and
http://llvm.org/devmtg/2012-11/Serebryany_TSan-MSan.pdf.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.