mailing list archives
Re: valgrind complains on uninitialised bytes
From: Vasily Kulikov <segoon () openwall com>
Date: Thu, 15 Aug 2013 17:32:57 +0400
On Tue, Aug 13, 2013 at 08:25 -0700, David Fifield wrote:
On Tue, Aug 13, 2013 at 12:23:15PM +0400, Vasily Kulikov wrote:
With --with-libpcap=included the bug is gone. Is it a bug in Ubuntu's
version of libpcap or in the nmap's way of libpcap's usage?
I think it is neither; rather it is that Valgrind doesn't know the way
setsockopt is used in this case. Nmap's version of libpcap might have
been patched to make the warning go away.
Oh, this is a known issue. I should have googled first, sorry for the
http://www.openwall.com - bringing security into open computing environments
Sent through the dev mailing list
Archived at http://seclists.org/nmap-dev/