https://bugs.kde.org/show_bug.cgi?id=422679
Bug ID: 422679
Summary: Support suppression file for --alloc-fn arguments to
massif
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: massif
Assignee: n...@valgrind.org
Reporter: bugzi...@tecnocode.co.uk
Target Milestone: ---
Just like memcheck supports suppression files to hide known/intentional memory
leaks, it would be useful if massif supported suppression files to provide
--alloc-fn arguments for common malloc() wrappers.
For example, I run massif for GLib applications using the following:
--alloc-fn=g_malloc --alloc-fn=g_object_new --alloc-fn=g_malloc0
--alloc-fn=g_malloc0_n --alloc-fn=g_malloc_n --alloc-fn=g_realloc
--alloc-fn=g_realloc_n --alloc-fn=g_slice_alloc --alloc-fn=g_slice_alloc0
--alloc-fn=g_type_create_instance --alloc-fn=g_object_new_internal
--alloc-fn=g_object_new_with_properties --alloc-fn=g_object_newv
--alloc-fn=g_object_new_valist --alloc-fn=g_try_malloc
--alloc-fn=g_try_malloc_n --alloc-fn=g_hash_table_realloc_key_or_value_array
--alloc-fn=realloc_arrays --alloc-fn=g_hash_table_resize
--alloc-fn=g_hash_table_maybe_resize --alloc-fn=g_hash_table_insert_node
--alloc-fn=g_hash_table_insert_internal --alloc-fn=g_hash_table_setup_storage
just so that various internal GLib wrappers around malloc() are ignored and the
output focuses on the code which is calling them.
It would be more convenient to be able to put these arguments in the shared
suppression file which GLib already installs for memcheck, so that users of
GLib don’t have to reinvent this list for themselves. Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
