Home
Pages 73
- Home
- AddressSanitizer
- AddressSanitizerAlgorithm
- AddressSanitizerAndDebugger
- AddressSanitizerAndroidPlatform
- AddressSanitizerAsDso
- AddressSanitizerBasicBlockTracing
- AddressSanitizerCallStack
- AddressSanitizerClangVsGCC (3.8 vs 6.0)
- AddressSanitizerClangVsGCC (5.0 vs 7.1)
- AddressSanitizerComparisonOfMemoryTools
- AddressSanitizerCompileTimeOptimizations
- AddressSanitizerContainerOverflow
- AddressSanitizerExampleGlobalOutOfBounds
- AddressSanitizerExampleHeapOutOfBounds
- AddressSanitizerExampleInitOrderFiasco
- AddressSanitizerExampleStackOutOfBounds
- AddressSanitizerExampleUseAfterFree
- AddressSanitizerExampleUseAfterReturn
- AddressSanitizerExampleUseAfterScope
- AddressSanitizerFlags
- AddressSanitizerForKernel
- AddressSanitizerFoundBugs
- AddressSanitizerHowToBuild
- AddressSanitizerHowToContribute
- AddressSanitizerIncompatiblity
- AddressSanitizerInHardware
- AddressSanitizerInitializationOrderFiasco
- AddressSanitizerIntelMemoryProtectionExtensions
- AddressSanitizerIntraObjectOverflow
- AddressSanitizerLeakSanitizer
- AddressSanitizerLeakSanitizerDesignDocument
- AddressSanitizerLeakSanitizerVsHeapChecker
- AddressSanitizerLogo
- AddressSanitizerManualPoisoning
- AddressSanitizerOnAndroid
- AddressSanitizerOneDefinitionRuleViolation
- AddressSanitizerPerformanceNumbers
- AddressSanitizerRunningSpecBenchmarks
- AddressSanitizerSupportedPlatforms
- AddressSanitizerTestSuite
- AddressSanitizerUseAfterReturn
- AddressSanitizerUseAfterScope
- AddressSanitizerWindowsPort
- AddressSanitizerZeroBasedShadow
- MemorySanitizer
- MemorySanitizerBootstrappingClang
- MemorySanitizerBuildingClangOnOlderSystems
- MemorySanitizerFAQ
- MemorySanitizerFoundBugs
- MemorySanitizerInstrumentingLibstdcxx
- MemorySanitizerLibcxxHowTo
- MemorySanitizerRunning
- MemorySanitizerUsingGit
- SanitizerCommonFlags
- ThreadSanitizerAboutRaces
- ThreadSanitizerAlgorithm
- ThreadSanitizerAtomicOperations
- ThreadSanitizerBenchmarkingApache
- ThreadSanitizerCppManual
- ThreadSanitizerDeadlockDetector
- ThreadSanitizerDetectableBugs
- ThreadSanitizerDevelopment
- ThreadSanitizerFlags
- ThreadSanitizerForKernel
- ThreadSanitizerForKernelReports
- ThreadSanitizerFoundBugs
- ThreadSanitizerGoManual
- ThreadSanitizerOnAndroid
- ThreadSanitizerPopularDataRaces
- ThreadSanitizerReportFormat
- ThreadSanitizerSuppressions
- ThreadSanitizerVolatileRanges
- Show 58 more pages…
Clone this wiki locally
Welcome!
This repository is an umbrella for the three repositories previously hosted on code.google.com:
- http://code.google.com/p/address-sanitizer/
- http://code.google.com/p/thread-sanitizer/
- http://code.google.com/p/memory-sanitizer/
Since those projects started, most of the code has been moved to the LLVM Compiler Infrastructure (http://llvm.org). Here reside some pieces of infrastructure and documentation.
Below are the links to the documentation for each project.
AddressSanitizer
AddressSanitizer (ASan) is a fast memory error detector. It finds use-after-free and {heap,stack,global}-buffer overflow bugs in C/C++ programs. Learn more:
- AddressSanitizer -- how to use the tool.
- LeakSanitizer -- leak detector
- AddressSanitizer page at clang.llvm.org
- AddressSanitizerAlgorithm -- how it works.
- AddressSanitizerHowToContribute -- if you want to help.
- Read if you are working on Chromium
- Watch the presentation from the LLVM Developer's meeting (Nov 18, 2011): Video, slides.
-
Our paper accepted to USENIX ATC 2012
- See also: our slides for USENIX ATC 2012
Your comments are welcome at address-sanitizer@googlegroups.com or in Google+
ThreadSanitizer
ThreadSanitizer is a fast data race detector for C/C++ and Go.
Check out:
Send comments/questions to thread-sanitizer@googlegroups.com
MemorySanitizer
A fast LLVM-based tool that detects the use of uninitialized memory.
- MemorySanitizer - more info
- LLVM Developer's meeting (April 29-30, 2013): slides, video