aboutsummaryrefslogtreecommitdiff
path: root/contrib/valgrind.supp
diff options
context:
space:
mode:
authorKiminuo <kiminuo@protonmail.com>2020-06-11 10:04:33 +0200
committerfanquake <fanquake@gmail.com>2022-02-03 18:35:52 +0800
commitb87f9c5edf3895df9650131fcf8551c3ad1d7301 (patch)
tree49452ef57938298ccc5f321cd2e7788b295b8b65 /contrib/valgrind.supp
parent41d7166c8a598b604aad6c6b1d88ad46e23be247 (diff)
build: remove boost::filesystem usage
Diffstat (limited to 'contrib/valgrind.supp')
-rw-r--r--contrib/valgrind.supp21
1 files changed, 0 insertions, 21 deletions
diff --git a/contrib/valgrind.supp b/contrib/valgrind.supp
index ece02dc24e..35f3d792ff 100644
--- a/contrib/valgrind.supp
+++ b/contrib/valgrind.supp
@@ -119,12 +119,6 @@
fun:wcsnrtombs
}
{
- Suppress wcsnrtombs warning (remove after removing boost::fs)
- Memcheck:Cond
- ...
- fun:_ZN5boost10filesystem6detail11unique_pathERKNS0_4pathEPNS_6system10error_codeE
-}
-{
Suppress boost warning
Memcheck:Leak
fun:_Znwm
@@ -135,21 +129,6 @@
fun:main
}
{
- Suppress boost::filesystem warning (fixed in boost 1.70: https://github.com/boostorg/filesystem/commit/bbe9d1771e5d679b3f10c42a58fc81f7e8c024a9)
- Memcheck:Cond
- fun:_ZN5boost10filesystem6detail28directory_iterator_incrementERNS0_18directory_iteratorEPNS_6system10error_codeE
- ...
- obj:*/libboost_filesystem.so.*
-}
-{
- Suppress boost::filesystem warning (could be related: https://stackoverflow.com/questions/9830182/function-boostfilesystemcomplete-being-reported-as-possible-memory-leak-by-v)
- Memcheck:Leak
- match-leak-kinds: reachable
- fun:_Znwm
- ...
- fun:_ZN5boost10filesystem8absoluteERKNS0_4pathES3_
-}
-{
Suppress boost still reachable memory warning
Memcheck:Leak
match-leak-kinds: reachable