"g_hash_table_new_full" triggering valgrind "still reachable" leaks regardless of glib.supp
Hi,
I'm using glib to use the GHashTable type, and I'm getting "reachable blocks" in leak summary when running valgrind: valgrind_log.txt
I tested it in a really simple code:
// gcc main.c -Wall $(pkg-config --cflags --libs glib-2.0)
// valgrind -s --leak-check=full --show-leak-kinds=all --suppressions=glib.supp ./a.out
#include <glib.h>
int main()
{
GHashTable* ht = g_hash_table_new_full(g_str_hash, g_str_equal, NULL, NULL);
g_hash_table_destroy(ht);
return 0;
}
Is this "reachable leak" not included in the glib.supp or am I doing something wrong? I'm using the glib.supp provided in 7 september 2023.
In my real code that I'm using glib I'm also getting the same number of reachable bytes and blocks. I'm also using destroy_notifiers for keys and/or values.
Thanks.
Edited by Caio Vinicius