summaryrefslogtreecommitdiff
path: root/tests/run-varlocs-self.sh
Commit message (Collapse)AuthorAgeFilesLines
* configure: Add --enable-sanitize-memoryIlya Leoshkevich2023-02-141-0/+5
| | | | | | | | | | | | | | | | | | | | Add support for clang Memory Sanitizer [1], which detects the usage of uninitialized values. While elfutils itself is already checked with valgrind, checking code that depends on elfutils requires elfutils to be built with MSan. MSan is not linked into shared libraries, and is linked into executables statically. Therefore, unlike the other sanitizers, MSan needs to be configured fairly early, since we need to drop -D_FORTIFY_SOURCE [2], -Wl,-z,defs and --no-undefined. Disable a few tests that run for more than 5 minutes due to test files being statically linked with MSan. [1] https://clang.llvm.org/docs/MemorySanitizer.html [2] https://github.com/google/sanitizers/issues/247 Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
* tests: Run run-varlocs-self.sh for object files with --exprlocs.Mark Wielaard2020-04-221-1/+3
| | | | | | | | | | | The varlocs test relies on finding addresses for the CUs, even in object files. This might not be true (for example when building with gcc -flto, which only emits partial, type only, debuginfo). Split running the self tests in running on executables and shared libraries as normal, but run object files with --exprlocs to test that output too (and not require addresses). Signed-off-by: Mark Wielaard <mark@klomp.org>
* tests: Add varlocs-self and exprlocs-self tests.Mark Wielaard2017-11-151-0/+22
Make sure the testcases (library functions they use) don't crash, triggers self-check/asserts or leaks memory under valgrind. This also helps making sure newer DWARF constructs are handled (when building with -gdwarf-5). Signed-off-by: Mark Wielaard <mark@klomp.org>