Nmap Development mailing list archives

Re: Nmap 4.85BETA8 Released!


From: David Fifield <david () bamsoftware com>
Date: Tue, 5 May 2009 13:49:40 -0600

On Wed, Apr 22, 2009 at 03:35:56PM +0200, Lionel Cons wrote:
Fyodor <fyodor () insecure org> writes:
Enjoy the new release!  And let us know on nmap-dev if you encounter
any problems!  See http://nmap.org/book/man-bugs.html.

FWIW, here are the compiler warnings I get on RHEL 5:

 ./gencode.c:3637: warning: 'b0' may be used uninitialized in this function
 ./savefile.c:1346: warning: ignoring return value of 'fwrite', declared with attribute warn_unused_result
 ./savefile.c:1347: warning: ignoring return value of 'fwrite', declared with attribute warn_unused_result
 scanner.l:361: warning: ignoring return value of 'fwrite', declared with attribute warn_unused_result
 rand.c:84: warning: ignoring return value of 'read', declared with attribute warn_unused_result
 intf.c:650: warning: pointer targets in passing argument 3 of 'getsockname' differ in signedness
 ip.c:43: warning: pointer targets in passing argument 5 of 'getsockopt' differ in signedness
 ncat_proxy.c:72: warning: dereferencing type-punned pointer will break strict-aliasing rules
 ncat_broker.c:276: warning: passing argument 4 of 'chat_filter' from incompatible pointer type
 output.cc:1333: warning: converting to 'int' from 'double'
 nse_binlib.cc:121: warning: converting to 'int' from 'lua_Number'

What compiler options are you using? I only get two of those:

intf.c:650: warning: pointer targets in passing argument 3 of 'getsockname' differ in signedness
ip.c:43: warning: pointer targets in passing argument 5 of 'getsockopt' differ in signedness

That's with GCC 4.3.1 and no CFLAGS or CPPFLAGS set in the environment.

David Fifield

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org


Current thread: