Sage Weil
f261687f29
valgrind: fix tcmalloc suppression for trusty
...
Fixes : #8225
Signed-off-by: Sage Weil <sage@inktank.com>
2014-04-28 15:57:36 -07:00
Sage Weil
bab84d45ab
Revert "valgrind.supp: be less picky about library versions"
...
This reverts commit f895d16c9e
.
2014-04-28 15:57:36 -07:00
Sage Weil
f895d16c9e
valgrind.supp: be less picky about library versions
...
...so that this works on trusty
Signed-off-by: Sage Weil <sage@inktank.com>
2014-03-29 09:39:46 -07:00
Sage Weil
c2bd8464d8
valgrind: fix msync suppression
...
Signed-off-by: Sage Weil <sage@inktank.com>
2014-02-05 11:26:41 -08:00
Sage Weil
be3ea71cdb
valgrind: another tcmalloc suppression
...
With this I can run a simple job with a normal build (not
notcmalloc) and valgrind does not complain. Fingers crossed!
Signed-off-by: Sage Weil <sage@inktank.com>
2014-02-01 22:05:14 -08:00
Sage Weil
9a9ee610bd
valgrind: ignore tcmalloc uninitialized memory
...
This is the main source of noise when running valgrind +
tcmalloc. Apparently there are other issues, so I think we
still need the notcmalloc gitbuilder, but this gets us part of
the way.
Signed-off-by: Sage Weil <sage@inktank.com>
2014-01-10 11:02:16 -08:00
Sage Weil
6b87147590
valgrind.supp: ignore libnss3 leaks
...
These just started popping up when I updated the notcmalloc gitbuilder, probably
because of an updated libnss version. Whitelist it!
Signed-off-by: Sage Weil <sage@inktank.com>
2013-12-30 10:12:37 -06:00
Sage Weil
c70e086b35
Revert "valgrind.supp: ignore libnss3 leaks"
...
This reverts commit 572dc88a7c
.
This didn't occur on next; I think there may be a real leak on the ceph
side.
2013-12-22 09:50:12 -08:00
Sage Weil
572dc88a7c
valgrind.supp: ignore libnss3 leaks
...
These just started popping up. Probably because I gave the
gitbuilders a kick?
Signed-off-by: Sage Weil <sage@inktank.com>
2013-12-21 22:21:49 -08:00
Sage Weil
c8ec9feca1
valgrind: fix libleveldb suppression on dynamically linked leveldb
...
(The function names don't show up here)
Signed-off-by: Sage Weil <sage@inktank.com>
2013-10-18 16:26:35 -07:00
Sage Weil
2acceef699
valgrind: suppress inet_ntop noise
...
See #6240
Signed-off-by: Sage Weil <sage@inktank.com>
2013-09-26 13:37:49 -07:00
Sage Weil
45ce9b0b54
valgrind: suppress curl, gnutlss, libfcgi leaks
...
Signed-off-by: Sage Weil <sage@inktank.com>
2013-07-27 07:49:11 -07:00
Sage Weil
4455f75d17
valgrind: give up and ignore all leveldb leaks
...
Hopefully if it is our fault we will have our own struct wrapping the
leveldb resource that we leak.
2013-06-19 09:08:17 -07:00
Sage Weil
ebd003bc82
valgrind: another leveldb leak
2013-06-17 13:53:10 -07:00
Sage Weil
d396096703
valgrind: make leveldb thread suppression more general
...
The thread can get created from a range of callers; ignore them all.
2013-06-11 19:34:33 -07:00
Sage Weil
c41e6ff5ba
valgrind: glibc/boost_thread leak suppressions
2013-06-08 22:26:31 -07:00
Sage Weil
028f1c709b
valgrind: more leveldb whitelisting
2013-06-07 21:20:08 -07:00
Sage Weil
64eb6df9fe
valgrind: add another leveldb suppression
2013-05-30 22:07:30 -07:00
Sage Weil
d029abfa5a
valgrind: update suppressions for leveldb, libc leaks from mon
...
These result in clean valgrind leak checks on the mon (at least with my
limited vstart testing).
2013-05-30 11:25:32 -07:00
Sage Weil
f9b4efeab1
valgrind.supp: deliverate onexit leak
2012-11-11 07:13:09 -08:00
Sage Weil
02d62d731d
valgrind.supp: ceph-fuse leak from libfuse
...
Signed-off-by: Sage Weil <sage@inktank.com>
2012-11-11 07:13:09 -08:00
tamil
39efbbcc2d
Suppress valgrind error "Invalid write 8"
...
Signed-off-by: tamil <tamil.muthamizhan@inktank.com>
2012-09-10 15:02:47 -07:00
Sage Weil
82cefa2477
suppress this valgrind error
...
<error>
<unique>0x4</unique>
<tid>1</tid>
<kind>InvalidWrite</kind>
<what>Invalid write of size 8</what>
<stack>
<frame>
<ip>0x400A299</ip>
<obj>/lib/x86_64-linux-gnu/ld-2.15.so</obj>
<fn>do_lookup_x</fn>
<dir>/build/buildd/eglibc-2.15/elf</dir>
<file>dl-lookup.c</file>
<line>250</line>
</frame>
<frame>
<ip>0x403122F</ip>
</frame>
<frame>
<ip>0x400A522</ip>
<obj>/lib/x86_64-linux-gnu/ld-2.15.so</obj>
<fn>_dl_lookup_symbol_x</fn>
<dir>/build/buildd/eglibc-2.15/elf</dir>
<file>dl-lookup.c</file>
<line>739</line>
</frame>
</stack>
<auxwhat>Address 0x7feffeec8 is on thread 1's stack</auxwhat>
</error>
pops up recently
2012-08-23 11:00:39 -07:00
Sage Weil
45fcca1fea
valgrind: add strptime suppressions
...
Precise's strptime triggers valgrind false positives.
Use ship_utilities to push the valgrind.supp file over, which is a bit
slippy.
2012-07-04 14:29:55 -07:00