When using sanitizers with gcc one can provide a list of exceptions/suppressions to deal with false positives and such. the suppression file format is poorly documented. Each suppression is of the form <pre class="prettyprint"><code>name_of_check:path_or_name </code></pre> What are the valid values for <code>name_of_check</code>?

I resorted to grabbing the values from the source code. These are based on gcc 10.1: <ul> <li> <code>ubsan</code>/<code>undefined</code> - see <code>libsanitizer/ubsan/ubsan_checks.inc</code> <ul> <li><code>undefined</code></li> <li><code>null</code></li> <li><code>pointer-overflow</code></li> <li><code>alignment</code></li> <li><code>object-size</code></li> <li><code>signed-integer-overflow</code></li> <li><code>unsigned-integer-overflow</code></li> <li><code>integer-divide-by-zero</code></li> <li><code>float-divide-by-zero</code></li> <li><code>invalid-builtin-use</code></li> <li><code>implicit-unsigned-integer-truncation</code></li> <li><code>implicit-signed-integer-truncation</code></li> <li><code>implicit-integer-sign-change</code></li> <li><code>shift-base</code></li> <li><code>shift-exponent</code></li> <li><code>bounds</code></li> <li><code>unreachable</code></li> <li><code>return</code></li> <li><code>vla-bound</code></li> <li><code>float-cast-overflow</code></li> <li><code>bool</code></li> <li><code>enum</code></li> <li><code>function</code></li> <li><code>returns-nonnull-attribute</code></li> <li><code>nonnull-attribute</code></li> <li><code>vptr</code></li> <li><code>cfi</code></li> </ul> </li> <li> <code>asan</code>/<code>address</code> - see <code>libsanitizer/asan/asan_suppressions.cpp</code> <ul> <li><code>interceptor_name</code></li> <li><code>interceptor_via_fun</code></li> <li><code>interceptor_via_lib</code></li> <li><code>odr_violation</code></li> </ul> </li> <li> <code>lsan</code>/<code>leak</code> - see <code>libsanitizer/lsan/lsan_common.cpp</code> <ul> <li><code>leak</code></li> </ul> </li> <li> <code>tsan</code>/<code>thread</code> - see <code>libsanitizer/tsan/tsan_suppressions.h</code> <ul> <li><code>none</code></li> <li><code>race</code></li> <li><code>race_top</code></li> <li><code>mutex</code></li> <li><code>thread</code></li> <li><code>signal</code></li> <li><code>called_from_lib</code></li> <li><code>deadlock</code></li> </ul> </li> </ul>

what are the valid sanitizer suppression strings for gcc?

When using sanitizers with gcc one can provide a list of exceptions/suppressions to deal with false positives and such.

the suppression file format is poorly documented.

Each suppression is of the form

name_of_check:path_or_name

What are the valid values for name_of_check?

What are GCC sanitizers?

The C/C++ compilers Clang/LLVM and GCC support so-called sanitizers. These sanitizers are built into the application code and track the execution at runtime to report execution errors. There are currently four interesting sanitizers: AddressSanitizer and LeakSanitizer.

What is AddressSanitizer GCC?

Address Sanitizer is a tool developed by Google detect memory access error such as use-after-free and memory leaks. It is built into GCC versions >= 4.8 and can be used on both C and C++ codes.

What is AddressSanitizer in c++?

Starting in Visual Studio 2019 version 16.9, the Microsoft C/C++ compiler (MSVC) and IDE supports the AddressSanitizer. AddressSanitizer (ASan) is a compiler and runtime technology that exposes many hard-to-find bugs with zero false positives: Alloc/dealloc mismatches and new / delete type mismatches.

What is error AddressSanitizer?

AddressSanitizer is a fast memory error detector. It consists of a compiler instrumentation module and a run-time library. The tool can detect the following types of bugs: Out-of-bounds accesses to heap, stack and globals. Use-after-free.

I resorted to grabbing the values from the source code. These are based on gcc 10.1:

ubsan/undefined - see libsanitizer/ubsan/ubsan_checks.inc
- undefined
- null
- pointer-overflow
- alignment
- object-size
- signed-integer-overflow
- unsigned-integer-overflow
- integer-divide-by-zero
- float-divide-by-zero
- invalid-builtin-use
- implicit-unsigned-integer-truncation
- implicit-signed-integer-truncation
- implicit-integer-sign-change
- shift-base
- shift-exponent
- bounds
- unreachable
- return
- vla-bound
- float-cast-overflow
- bool
- enum
- function
- returns-nonnull-attribute
- nonnull-attribute
- vptr
- cfi
asan/address - see libsanitizer/asan/asan_suppressions.cpp
- interceptor_name
- interceptor_via_fun
- interceptor_via_lib
- odr_violation
lsan/leak - see libsanitizer/lsan/lsan_common.cpp
- leak
tsan/thread - see libsanitizer/tsan/tsan_suppressions.h
- none
- race
- race_top
- mutex
- thread
- signal
- called_from_lib
- deadlock

what are the valid sanitizer suppression strings for gcc?

Tags:

gcc

address-sanitizer

sanitizer

thread-sanitizer

leak-sanitizer

GranBurguesa

People also ask

1 Answers

GranBurguesa

Recent Activity

Donate For Us

what are the valid sanitizer suppression strings for gcc?

Tags:

gcc

address-sanitizer

sanitizer

thread-sanitizer

leak-sanitizer

GranBurguesa

People also ask

1 Answers

GranBurguesa

Related questions

Recent Activity

Donate For Us