fish-shell/build_tools/lsan_suppressions.txt

# LSAN can detect leaks tracing back to __asan::AsanThread::ThreadStart (probably caused by our
# threads not exiting before their TLS dtors are called). Just ignore it.
leak:AsanThread

# ncurses leaks allocations freely as it assumes it will be running throughout. Ignore these.
leak:tparm
leak:_nc_doalloc
Add LSAN suppressions file Suppress TLS variable leaks caused by outstanding background threads by suppressing the ASAN interposer functions. This is possible because because we're now using use_tls=1. ----------------------- Direct leak of 64 byte(s) in 2 object(s) allocated from: #0 0x5627a1f0cc86 in __interceptor_realloc (/home/runner/work/fish-shell/fish-shell/build/fish_tests+0xb9fc86) (BuildId: da87d16730727369ad5fa46052d10337d6941fa9) #1 0x7f04d8800f79 in pthread_getattr_np (/lib/x86_64-linux-gnu/libc.so.6+0x95f79) (BuildId: 69389d485a9793dbe873f0ea2c93e02efaa9aa3d) #2 0x5627a1f2f664 in __sanitizer::GetThreadStackTopAndBottom(bool, unsigned long, unsigned long) (/home/runner/work/fish-shell/fish-shell/build/fish_tests+0xbc2664) (BuildId: da87d16730727369ad5fa46052d10337d6941fa9) #3 0x5627a1f2fb83 in __sanitizer::GetThreadStackAndTls(bool, unsigned long, unsigned long, unsigned long, unsigned long) (/home/runner/work/fish-shell/fish-shell/build/fish_tests+0xbc2b83) (BuildId: da87d16730727369ad5fa46052d10337d6941fa9) #4 0x5627a1f19a0d in __asan::AsanThread::SetThreadStackAndTls(__asan::AsanThread::InitOptions const) (/home/runner/work/fish-shell/fish-shell/build/fish_tests+0xbaca0d) (BuildId: da87d16730727369ad5fa46052d10337d6941fa9) #5 0x5627a1f19615 in __asan::AsanThread::Init(__asan::AsanThread::InitOptions const) (/home/runner/work/fish-shell/fish-shell/build/fish_tests+0xbac615) (BuildId: da87d16730727369ad5fa46052d10337d6941fa9) #6 0x5627a1f19b01 in __asan::AsanThread::ThreadStart(unsigned long long) (/home/runner/work/fish-shell/fish-shell/build/fish_tests+0xbacb01) (BuildId: da87d16730727369ad5fa46052d10337d6941fa9) #7 0x7f04d87ffb42 (/lib/x86_64-linux-gnu/libc.so.6+0x94b42) (BuildId: 69389d485a9793dbe873f0ea2c93e02efaa9aa3d) #8 0x7f04d88919ff (/lib/x86_64-linux-gnu/libc.so.6+0x1269ff) (BuildId: 69389d485a9793dbe873f0ea2c93e02efaa9aa3d) 2023-05-02 09:27:38 +08:00			`# LSAN can detect leaks tracing back to __asan::AsanThread::ThreadStart (probably caused by our`
			`# threads not exiting before their TLS dtors are called). Just ignore it.`
			`leak:AsanThread`

			`# ncurses leaks allocations freely as it assumes it will be running throughout. Ignore these.`
			`leak:tparm`
Suppress _nc_doalloc memory leak With the next commit, if I run docker/docker_run_tests.sh --shell-after docker/jammy-asan-clang.Dockerfile I get this in test_string.fish and test_git.fish: ================================================================= ==8339==ERROR: LeakSanitizer: detected memory leaks Direct leak of 72 byte(s) in 1 object(s) allocated from: #0 0x55a8a637eb45 in realloc /rustc/llvm/src/llvm-project/compiler-rt/lib/asan/asan_malloc_linux.cpp:85:3 #1 0x7facb841b6cc in _nc_doalloc (/lib/x86_64-linux-gnu/libtinfo.so.6+0x106cc) (BuildId: e22ba7829a55a0dec2201a0b6dac7ba236118561) SUMMARY: AddressSanitizer: 72 byte(s) leaked in 1 allocation(s). Strangely there is no tparm in the call stack. It does not seem to happen in CI. 2024-01-12 21:19:09 +08:00			`leak:_nc_doalloc`