more tsan suppressions

Change-Id: I58a5f1e23980720615180640529af31205417cd4
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/130748
Tested-by: Jenkins
Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>
This commit is contained in:
Noel Grandin 2022-03-01 11:09:49 +02:00
parent 744e6c0b75
commit eb968c4f6b

View file

@ -25,9 +25,14 @@ race:__vsnprintf_chk
# right now, I'm not interested in deadlocks at all, too many false+
deadlock:
# This is checking SAL_STRING_IS_STATIC, which is safe because that is written at compile time
# This is checking SAL_STRING_IS_STATIC, which is safe because that is written at compile time.
# Depending on the optimisation/debug level, the call stack may have different leaves, hence
# specifying this in more than one way.
race:rtl::str::acquire<_rtl_uString>
race:rtl::str::release<_rtl_uString>
race:rtl_uString_acquire
race:rtl_uString_release
race:rtl_uString_assign
# I've convinced myself this is a false+, caused by ping-ponging the buffer between two
# threads, but I might be wrong