mem-leak freeing g_strdup

我試圖釋放g_strdup，但我不知道我做錯了什麼。mem-leak freeing g_strdup

使用valgrind --tool=memcheck --leak-check=yes ./a.out我不斷收到：

==4506== 40 bytes in 10 blocks are definitely lost in loss record 2 of 9 
==4506== at 0x4024C1C: malloc (vg_replace_malloc.c:195) 
==4506== by 0x40782E3: g_malloc (in /lib/libglib-2.0.so.0.2200.3) 
==4506== by 0x4090CA8: g_strdup (in /lib/libglib-2.0.so.0.2200.3) 
==4506== by 0x8048722: add_inv (dup.c:26) 
==4506== by 0x80487E6: main (dup.c:47) 

==4506== 504 bytes in 1 blocks are possibly lost in loss record 4 of 9 
==4506== at 0x4023E2E: memalign (vg_replace_malloc.c:532) 
==4506== by 0x4023E8B: posix_memalign (vg_replace_malloc.c:660) 
==4506== by 0x408D61D: ??? (in /lib/libglib-2.0.so.0.2200.3) 
==4506== by 0x408E5AC: g_slice_alloc (in /lib/libglib-2.0.so.0.2200.3) 
==4506== by 0x4061628: g_hash_table_new_full (in /lib/libglib-2.0.so.0.2200.3) 
==4506== by 0x40616C7: g_hash_table_new (in /lib/libglib-2.0.so.0.2200.3) 
==4506== by 0x8048795: main (dup.c:42)

我已經嘗試了不同的方式來解脫出來，但沒有成功爲止。我會感謝任何幫助。謝謝

順便說一句：它編譯和運行良好。

#include <stdio.h> 
#include <string.h> 
#include <stdlib.h> 
#include <glib.h> 
#include <stdint.h> 

struct s { 
    char *data; 
}; 

static GHashTable *hashtable1; 
static GHashTable *hashtable2; 

static void add_inv(GHashTable *table, const char *key) 
{ 
    gpointer old_value, old_key; 
    gint value; 

    if(g_hash_table_lookup_extended(table,key, &old_key, &old_value)){ 
     value = GPOINTER_TO_INT(old_value); 
     value = value + 2; 
     /*g_free (old_key);*/ 
    } else { 
     value = 5; 
    } 
    g_hash_table_replace(table, g_strdup(key), GINT_TO_POINTER(value)); 
} 

static void print_hash_kv (gpointer key, gpointer value, gpointer user_data){ 
    gchar *k = (gchar *) key; 
    gchar *h = (gchar *) value; 
    printf("%s: %d \n",k, h); 
} 

int main(int argc, char *argv[]){ 

    struct s t; 

    t.data = "bar"; 

    int i,j; 
    hashtable1 = g_hash_table_new(g_str_hash, g_str_equal); 
    hashtable2 = g_hash_table_new(g_str_hash, g_str_equal); 

    for(i=0;i<10;i++){ 
     add_inv(hashtable1, t.data); 
     add_inv(hashtable2, t.data); 
    } 

    /*free(t.data);*/ 
    /*free(t.data);*/ 

    g_hash_table_foreach (hashtable1, print_hash_kv, NULL); 
    g_hash_table_foreach (hashtable2, print_hash_kv, NULL); 

    g_hash_table_destroy(hashtable1); 
    g_hash_table_destroy(hashtable2); 

    return 0; 
}

來源

2010-03-13 Mike

謝謝。看起來像你們提到的那樣工作： hashtable1 = g_hash_table_new_full（g_str_hash，g_str_equal，（GDestroyNotify）free_key_value，NULL）; – Mike 2010-03-13 18:18:41

g_strdup（鍵）分配內存，但沒有釋放內存。

您應該將自己的key_destroy_func提供給g_hash_table_new_full而不是使用g_hash_table_new。

來源

2010-03-13 18:01:15

-1

爲什麼你g_strdup()你把每一個鍵放入散列表？你需要這樣做嗎？如果GTK要求你在hashtable中重複每個char*的密鑰，我敢打賭它在做g_hash_table_destroy()時會釋放它。

檢查GTK備份。

來源

2010-03-13 18:04:53 pajton

mem-leak freeing g_strdup

回答

相關問題