Nmap Development: How to debug a segmentation fault

From: Douglas F. Calvert <dfc_at_anize.org>
Date: Thu, 09 Nov 2006 06:06:11 -0500

Hello,
I am testing out nmap4.20a11 with linux 2.6.19-rc5. I am getting a lot
of segmentation faults when I scan with:

nmap -sV -O -n -oA basename -PE --version_all --allports
--randomize_hosts -n -v -v --max_retries 3 --log-errors -d5
1.1.14-16.1-254 > nmap.out 2>&1

Right before nmap seg faults there are a lot of lines like this in the
file containing the redirected output:

pcap wait time is 2000.
Host 1.1.15.128. ProbesToSend 0: ProbesActive 1
Host 1.1.15.151. ProbesToSend 0: ProbesActive 1
Host 1.1.14.182. ProbesToSend 0: ProbesActive 0

And basename looks like

(i am not exactly sure why the redirected output is different from
basename because --log-errors is on):

RCVD (54.2690s) ICMP 1.1.14.16 > 192.168.10.22 port unreachable
(type=3/code=3) ttl=60 id=2204 iplen=56
RCVD (54.2720s) TCP 1.1.14.11:23 > 192.168.10.22:61727 R ttl=60 id=32313
iplen=40 seq=4245400144 win=8192
RCVD (54.2720s) TCP 1.1.14.6:23 > 192.168.10.22:61727 R ttl=60 id=3067
iplen=40 seq=4245400144 win=8192
SENT (54.2810s) TCP 192.168.10.22:61726 > 1.1.14.3:80 SFPU ttl=44
id=23448 iplen=60 seq=758055748 win=256 <wsacle 10,nop,mss
265,timestamp 4294967295 0,sackOK>
SENT (54.2810s) TCP 192.168.10.22:61728 > 1.1.14.6:1 S ttl=49 id=4609
iplen=60 seq=758055748 win=31337 <wsacle 10,nop,mss 265,timestamp
4294967295 0,sackOK>
SENT (54.2810s) TCP 192.168.10.22:61728 > 1.1.14.11:1 S ttl=54 id=16472
iplen=60 seq=758055748 win=31337 <wsacle 10,nop,mss 265,timestamp
4294967295 0,sackOK>
RCVD (54.2960s) TCP 1.1.14.3:80 > 192.168.10.22:61726 A ttl=60 id=55239
iplen=40 seq=2122688445 win=8192 ack=758055750
RCVD (54.3000s) TCP 1.1.14.6:1 > 192.168.10.22:61728 RA ttl=60 id=3068
iplen=40 seq=0 win=0 ack=758055749
RCVD (54.3000s) TCP 1.1.14.11:1 > 192.168.10.22:61728 RA ttl=60 id=32314
iplen=40 seq=0 win=0 ack=758055749
SENT (54.3090s) TCP 192.168.10.22:61727 > 1.1.14.3:80 A ttl=56 id=24772
iplen=60 seq=758055748 win=1024 ack=4245400144 <wsacle 10,nop,mss
265,timestamp 4294967295 0,sackOKl

How would I go about figuring out why nmap is dying?

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