Re: [Valgrind-users] expected results for regtest

[John R. <jr...@bi...>]

Mark Wielaard wrote:

> The issue I believe is that unless we have the full symtab (from the
> separate libstdc++-debuginfo package) we don't know the name of the
> function. For memcheck the following suppression seems to work, with
> a variant that is stripped and one with full symtab debug symbols:
>
> {
>     malloc-leaks-cxx-stl-string-classes
>     Memcheck:Leak
>     match-leak-kinds: reachable
>     fun:malloc
>     obj:*/*lib*/libstdc++.so*
>     fun:call_init.part.0
>     fun:call_init
>     fun:_dl_init
>     obj:/usr/*lib*/ld-2.*.so
> }
>
> {
>    malloc-leaks-cxx-stl-string-classes-debug
>    Memcheck:Leak
>    match-leak-kinds: reachable
>    fun:malloc
>    fun:pool
>    fun:__static_initialization_and_destruction_0
>    fun:_GLOBAL__sub_I_eh_alloc.cc
>    fun:call_init.part.0
>    fun:call_init
>    fun:_dl_init
>    obj:/usr/*lib*/ld-2.*.so
> }
>
> I don't know how to do a similar dual suppression using the massif
> --ignore-fn option.

Does the frame-level wildcard "..." work, while still catching real errors?

{
   malloc-leaks-cxx-stl-string-classes-debug
   Memcheck:Leak
   match-leak-kinds: reachable
   fun:malloc
   ...
   fun:call_init.part.0
   fun:call_init
   fun:_dl_init
   obj:/usr/*lib*/ld-2.*.so
}