Nmap Development mailing list archives
Re: Possible memory leaks in libnetutil
From: "Luis MartinGarcia." <luis.mgarc () gmail com>
Date: Tue, 10 Aug 2010 01:12:07 +0200
On 08/10/2010 01:06 AM, Brandon Enright wrote:
On Tue, 10 Aug 2010 01:01:15 +0200 or thereabouts "Luis MartinGarcia." <luis.mgarc () gmail com> wrote:Hi again,Valgrind also showed possible memory leaks in libnetutil. I haven't look at this in detail but I think there should be a way to avoid the valgrind warnings like:[...]The thing is that getinterfaces() caches the list of interfaces so subsequent calls don't have to use dnet or do ioctl() calls again. I guess getsysroutes() does something similar. However, it may be nice to provide some helpers or modify the functions in some way so we can free() any allocated memory and avoid the warnings.Regards,Luis MartinGarcia.Hi Luis, You didn't show the command you were running. This certainly wouldn't be the first memory leak either but are you running Nmap with --release-memory? About a year ago I was tracking down a few memory leaks that turned went away with the --release-memory option. Regards,
Hi Brandon, Sorry, I forgot to mention it. I was running Nping, not nmap. Regards, Luis MartinGarcia. _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
Current thread:
- Possible memory leaks in libnetutil Luis MartinGarcia. (Aug 09)
- Re: Possible memory leaks in libnetutil Brandon Enright (Aug 09)
- Re: Possible memory leaks in libnetutil Luis MartinGarcia. (Aug 09)
- Re: Possible memory leaks in libnetutil Fyodor (Aug 10)
- Re: Possible memory leaks in libnetutil Brandon Enright (Aug 09)