hardinfo crashed with SIGSEGV in free()

StacktraceTop:free () from /lib/tls/i686/cmov/libc.so.6
IA__g_free (mem=0x83bfe60) at /build/buildd/glib2.0-2.14.1/glib/gmem.c:187
g_hash_node_destroy (hash_node=0x82d8330, key_destroy_func=0,
g_hash_table_foreach_remove_or_steal (hash_table=0x8385d60, func=0xb7d37160 <IA__gtk_true>,
module_selected_show_info (entry=0x8097c50, reload=0) at shell.c:1012

Could you please test the code in the SVN repository? If you need help compiling the code by yourself just ask me.

Can you send me a tar.gz package? My University blocks external svn access...

no, I install hardinfo from repository...

2007/10/22, Rafael Sachetto <email address hidden>:
>
> Can you send me a tar.gz package? My University blocks external svn
> access...
>
> --
> hardinfo crashed with SIGSEGV in free()
> https://bugs.launchpad.net/bugs/144903
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

Hi.

   Not sure if this solves this issue for you all, in my case it did the trick though.

I modified the file shell.c, near line 1014, from this:

    /* recreate the iter hash table */
    if (!reload) {
        if (update_tbl) {
            g_hash_table_foreach_remove( update_tbl, (GHRFunc)gtk_true, NULL);
        } else {
            update_tbl = g_hash_table_new_full(g_str_hash, g_str_equal, g_free, g_free);
        }
    }

To this:

    /* recreate the iter hash table */
    if (!reload) {
        if (update_tbl) {
            g_hash_table_foreach_remove( update_tbl, (GHRFunc)gtk_true, NULL);
        } else {
            /*
              GNR - October 24th, 2007.
                Replacing g_hash_table_new_full with g_hash_table_new solves the SIGSEGV
                error!
            */
// update_tbl = g_hash_table_new_full(g_str_hash, g_str_equal, g_free, g_free);
            update_tbl = g_hash_table_new(g_str_hash, g_str_equal);
        }
    }

That is, I replaced the call to g_hash_table_new_full with a call to g_hash_table_new

I'm no GTK programmer, so I don't know what could be causing the error, as the only difference I see is the calls to g_free for disposing the key/value pairs.

Anyway, hope this helps somebody.

This has been fixed in the latest 0.4.2.3 release.

Marking with Fix Releases as this has been fixed in the latest 0.4.2.3 release.