On 02/22/2017 03:11 PM, Dario Lombardo wrote:
On Wed, Feb 22, 2017 at 3:55 PM, Evan Huus <[email protected] <mailto:[email protected]>> wrote: checkAPI doesn't allow free because it also doesn't allow malloc; if the malloced memory is coming from library internals somewhere, does the library itself have a cleanup method we could call instead? Unfortunately no. This is a corner case checkAPI is not able to handle. A solution would be to try to push a cleanup function upstream, but I don't know how they are about that. And I guess it would take time, while we have a pending crash.
Maybe this will do: https://code.wireshark.org/review/#/c/20246/2 ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
