Nmap Crash with sudo on Mac OS X

[Vincent Dumont <dumontv7 () gmail com>]

Hello devs,

I am writing to you today because I just discovered that nmap crashes every time it is called with sudo (root 
privileges) on Mac OS X.
You can find the crash report attached(found in Console.app).

As the following valgrind inspection confirms this, it seems to be a jump to address 0x0.
I spent a few hours on it without any success, so if you could test nmap with sudo and return feedback, it would be 
really great.
This issue happens even after reinstalling Nmap 7.12SVN.

Starting Nmap 7.12SVN ( https://nmap.org ) at 2016-06-22 19:47 CEST
--37341-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 8 times)
==37341== Jump to the invalid address stated on the next line
==37341==    at 0x0: ???
==37341==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==37341==
==37341==
==37341== Process terminating with default action of signal 11 (SIGSEGV)
==37341==  Bad permissions for mapped region at address 0x0
==37341==    at 0x0: ???
==37341==
==37341== HEAP SUMMARY:
==37341==     in use at exit: 5,563,403 bytes in 40,237 blocks
==37341==   total heap usage: 45,172 allocs, 4,935 frees, 17,308,137 bytes allocated
==37341==
==37341== LEAK SUMMARY:
==37341==    definitely lost: 232 bytes in 4 blocks
==37341==    indirectly lost: 76 bytes in 5 blocks
==37341==      possibly lost: 2,064 bytes in 1 blocks
==37341==    still reachable: 5,541,176 bytes in 40,054 blocks
==37341==                       of which reachable via heuristic:
==37341==                         newarray           : 6,152 bytes in 1 blocks
==37341==         suppressed: 19,855 bytes in 173 blocks
==37341== Rerun with --leak-check=full to see details of leaked memory
==37341==
==37341== For counts of detected and suppressed errors, rerun with: -v
==37341== Use --track-origins=yes to see where uninitialised values come from
==37341== ERROR SUMMARY: 489 errors from 3 contexts (suppressed: 0 from 0)

I will do more investigations and work on it as soon as possible.

Talk to you soon, 

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