【问题标题】:mem-leak freeing g_strdup内存泄漏释放 g_strdup
【发布时间】:2011-01-27 05:11:58
【问题描述】:

我正在尝试释放 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;
}

【问题讨论】:

  • 谢谢。似乎像你们提到的那样工作: hashtable1 = g_hash_table_new_full(g_str_hash, g_str_equal, (GDestroyNotify) free_key_value,NULL);

标签: c memory-leaks valgrind strdup


【解决方案1】:

g_strdup(key) 分配内存,但没有人释放该内存。

您可能应该向 g_hash_table_new_full 提供自己的 key_destroy_func,而不是使用 g_hash_table_new。

【讨论】:

    【解决方案2】:

    为什么g_strdup() 你放入哈希表的每个键?你需要这样做吗?如果 GTK 要求您复制哈希表中的每个 char* 键,我敢打赌它会在执行 g_hash_table_destroy() 时释放它们。

    检查 GTK 文档。

    【讨论】:

      猜你喜欢
      • 2012-06-08
      • 2014-08-26
      • 1970-01-01
      • 2018-06-04
      • 2014-09-19
      • 1970-01-01
      • 2010-12-04
      • 1970-01-01
      • 1970-01-01
      相关资源
      最近更新 更多