Home page logo
/

nmap-dev logo Nmap Development mailing list archives

Re: valgrind complains on uninitialised bytes
From: "Luis MartinGarcia." <luis.mgarc () gmail com>
Date: Tue, 13 Aug 2013 17:37:16 +0200

Hi,

Yeah. I reported this to the tcpdump guys a long time ago (see
https://github.com/the-tcpdump-group/libpcap/issues/147). They decided
not to apply the patch as they consider it Valgrind's fault (I believe
they are right). I got the response like a whole year after I reported
it, so I never bothered to contact Valgrind's development team.

Regards,

Luis MartinGarcia.



On 08/13/2013 05:25 PM, 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.

https://github.com/mcr/libpcap/issues/25
http://seclists.org/nmap-dev/2010/q3/796
https://bugs.kde.org/show_bug.cgi?id=318203

David Fifield
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/


_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/


  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
AlienVault