Nmap Development mailing list archives
Segfault with large exclude list
From: Kurt Grutzmacher <grutz () jingojango net>
Date: Fri, 5 Aug 2005 00:15:13 -0500
Yes this isn't the most efficient way to do a scan but it's not for business, just for fun. Using superduper 3.83_DC1 release. ./nmap -sV -sS -PS:80 -R -p 80 172.16.0.0/14 -v -v -T2 --randomize_hosts -oA ../everybody_dance --scan_delay 500 --max_hostgroup 2 --excludefile ../scanned_1 -d -d -d -d [... lots of stuff ...] doing 0.0.0.0 = 172.16.116.2 doing 0.0.0.0 = 172.16.116.209 doing 0.0.0.0 = 172.16.126.204 doing 0.0.0.0 = 172.16.0.19 doing 0.0.0.0 = 172.16.7.31 Segmentation fault grutz@blaat nmap-3.83.DC1 $ wc ../scanned_1 2590 2590 32657 ../scanned_1
From within GDB:
Program received signal SIGSEGV, Segmentation fault. 0x080739a5 in TargetGroup::skip_range(TargetGroup::_octet_nums) (this=0x40345444, octet=FIRST_OCTET) at TargetGroup.cc:342 342 current[i] = 0; -- ..:[ grutz at jingojango dot net ]:.. GPG fingerprint: 5FD6 A27D 63DB 3319 140F B3FB EC95 2A03 8CB3 ECB4 "There's just no amusing way to say, 'I have a CISSP'." _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev
Current thread:
- Segfault with large exclude list Kurt Grutzmacher (Aug 04)