Wireshark mailing list archives

Re: Freeing memory of se_alloc'ated object


From: Guy Harris <guy () alum mit edu>
Date: Sun, 1 May 2011 12:21:02 -0700


On May 1, 2011, at 12:15 PM, Max wrote:

But am I the only guy who finds this ugly?

No.

In this situation  it would
be perfect if se_alloc() engine could call a callback with a user
supplied argument before it starts to deallocate anything.

The init mechanism was created before the ephemeral memory stuff even existed, and has never been updated.

Some better mechanism, such as the one you suggest, would probably be a good idea.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe


Current thread: