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

Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

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.

From: "Mike Frisch" <mfrisch@xxxxxxxxxx>

Date: Fri, 7 Oct 2005 10:06:24 -0400 (EDT)

> 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.

Ahh, thanks...  this should probably be documented somewhere.  There is no
mention of "se_alloc()" in the 'doc' subdir of the source tree.

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

References:
- [Ethereal-dev] packet-rpc.c: where are hash table keys freed?
  - From: Mike Frisch
- Re: [Ethereal-dev] packet-rpc.c: where are hash table keys freed?
  - From: LEGO

Prev by Date: [Ethereal-dev] Buildbot crash output
Next by Date: [Ethereal-dev] Compile error - 'ETHER_PREFIX' : undeclared identifier
Previous by thread: Re: [Ethereal-dev] packet-rpc.c: where are hash table keys freed?
Next by thread: Re: [Ethereal-dev] packet-rpc.c: where are hash table keys freed?
Index(es):
- Date
- Thread

© Wireshark Foundation · Privacy Policy

Facebook·Mastodon·Twitter·YouTube