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
}
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
