https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3725
--- Comment #5 from Jaap Keuter <jaap.keuter@xxxxxxxxx> 2010-08-03 08:10:54 CEST ---
(In reply to comment #3)
> (In reply to comment #2)
> > That in itself is not a problem. As long as there's a free for every
> > allocation. Sometimes you can assure that easily, sometimes not. That's where
> > ep_/se_ memory comes in.
>
> What happens if memory is allocated then the packet is malformed before the
> free occurs? Or what happens if memory is allocated, but the packet is
> truncated due to the snaplen and dissection is aborted before the memory can be
> freed?
Then you cannot make this assurance, hence should resort to other means, like
ep_/se_ memory. The problem is that the ways exceptions can occur are not
always clear (in the minds eye of the developer). That's where to problem comes
in.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.