Hello, GLib/GTK+ don't seem to provide a Valgrind suppression file upstream. At the following wiki page: https://wiki.gnome.org/Valgrind
I see that there is: 1) https://people.gnome.org/~johan/gtk.suppression 2) https://github.com/dtrebbien/GNOME.supp 1) is for Gtk+ 2.12, according to the comment at the top. 2) is more recent, but not up-to-date, for example I see: ==6677== 16 bytes in 1 blocks are possibly lost in loss record 1,488 of 6,253 ==6677== at 0x4C2DA60: calloc (vg_replace_malloc.c:711) ==6677== by 0x74648FF: g_malloc0 (gmem.c:124) ==6677== by 0x7464BC7: g_malloc0_n (gmem.c:355) ==6677== by 0x6DD922B: type_set_qdata_W (gtype.c:3718) ==6677== by 0x6DD9528: type_add_flags_W (gtype.c:3783) ==6677== by 0x6DD79C6: g_type_register_fundamental (gtype.c:2659) ==6677== by 0x6DB59F3: _g_enum_types_init (genums.c:124) ==6677== by 0x6DDA683: gobject_init (gtype.c:4426) ==6677== by 0x6DDA6AD: gobject_init_ctor (gtype.c:4487) ==6677== by 0x400FDA9: call_init.part.0 (in /usr/lib64/ld-2.23.so) ==6677== by 0x400FEBA: _dl_init (in /usr/lib64/ld-2.23.so) ==6677== by 0x4000CB9: ??? (in /usr/lib64/ld-2.23.so) I think all things initialized in gobject_init_ctor() can be suppressed, the same for other "ctor" functions. So, is there an up-to-date Valgrind suppression file somewhere? Or is GNOME.supp the most up-to-date? I'm aware of: "Make GLib valgrind friendly" https://bugzilla.gnome.org/show_bug.cgi?id=627423 But in that bug, there is no significant activity since 2013, so if there is an up-to-date suppression file, it might make sense to include it upstream, and install it. Thanks in advance, Sébastien _______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
