Ethereal-dev: Re: [Ethereal-dev] packet-rpc.c: where are hash table keys freed?

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: LEGO <luis.ontanon@xxxxxxxxx>
Date: Thu, 6 Oct 2005 23:07:14 +0200
The keys and values of rpc_calls are allocated using se_alloc(), which
is automatically freed before starting the next session, so there's no
need to free them explicitly.

On 10/6/05, Mike Frisch <mfrisch@xxxxxxxxxx> wrote:
> rpc_calls is a glib hash table allocated using g_hash_table_new().  As per
> the documentation for glib, the keys and/or values should be freed prior
> to calling g_hash_table_destroy().
>
> (ref:
> http://developer.gnome.org/doc/API/2.0/glib/glib-Hash-Tables.html#g-hash-table-new)
>
> Does this mean that memory allocated for the keys and values in rpc_calls
> is leaked when/if the table is destroyed?  This seems too obvious as a
> memory leak, but I cannot see anywhere they're freed.
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>


--
This information is top security. When you have read it, destroy yourself.
-- Marshall McLuhan