Nmap Development mailing list archives
Re: nmap crash -- NmapOutputTable.cc:153: void NmapOutputTable::addItem(unsigned int, unsigned int, bool, const char*, int): Assertion `row < numRows' failed.
From: David Fifield <david () bamsoftware com>
Date: Mon, 18 Jan 2010 11:34:51 -0700
On Mon, Jan 18, 2010 at 01:01:32PM -0500, Jon Kibler wrote:
Jon Kibler wrote:I am having nmap crash and getting empty files for output:# nmap -sS -sV -sU -sC -oA cts -O -p- -T4 --min-rtt-timeout=1 --max-rtt-timeout=8 --initial-rtt-timeout=4 --min-parallelism=64 --max-parallelism=128 --max-retries=3 --version-light 10.22.149.132 WARNING: You specified a round-trip time timeout (8 ms) that is EXTRAORDINARILY SMALL. Accuracy may suffer.Starting Nmap 5.10BETA2 ( http://nmap.org ) at 2010-01-16 21:48 GMT Nmap scan report for 10.22.149.132 Host is up (0.00042s latency). Not shown: 65533 open|filtered ports, 65526 filtered ports nmap: NmapOutputTable.cc:153: void NmapOutputTable::addItem(unsigned int, unsigned int, bool, const char*, int): Assertion `row < numRows' failed. AbortedI hate to respond to my own email... but I notice that this had been a problem that was previously fixed in 4.01. I have rerun the scan with -d, and it doesn't seem to tell anything not already known (attaching log... if it passes filter). What can I do to help get this debugged?
See if you can simplify the command line and still get the crash. For example, does it still happen if you don't use -sV? What if you narrow the port range with -p? The most likely culprits are the options that add rows to the ports table: -sS -sU -sC. If you can rule any of those out it would help. David Fifield _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://seclists.org/nmap-dev/
Current thread:
- nmap crash Jon Kibler (Jan 16)
- Re: nmap crash -- NmapOutputTable.cc:153: void NmapOutputTable::addItem(unsigned int, unsigned int, bool, const char*, int): Assertion `row < numRows' failed. Jon Kibler (Jan 18)
- Re: nmap crash -- NmapOutputTable.cc:153: void NmapOutputTable::addItem(unsigned int, unsigned int, bool, const char*, int): Assertion `row < numRows' failed. David Fifield (Jan 18)
- Message not available
- Re: nmap crash -- NmapOutputTable.cc:153: void NmapOutputTable::addItem(unsigned int, unsigned int, bool, const char*, int): Assertion `row < numRows' failed. David Fifield (Jan 20)
- Re: nmap crash -- NmapOutputTable.cc:153: void NmapOutputTable::addItem(unsigned int, unsigned int, bool, const char*, int): Assertion `row < numRows' failed. Jon Kibler (Jan 20)
- Re: nmap crash -- NmapOutputTable.cc:153: void NmapOutputTable::addItem(unsigned int, unsigned int, bool, const char*, int): Assertion `row < numRows' failed. David Fifield (Jan 21)
- Re: nmap crash -- NmapOutputTable.cc:153: void NmapOutputTable::addItem(unsigned int, unsigned int, bool, const char*, int): Assertion `row < numRows' failed. Jon Kibler (Feb 01)
- Re: nmap crash -- NmapOutputTable.cc:153: void NmapOutputTable::addItem(unsigned int, unsigned int, bool, const char*, int): Assertion `row < numRows' failed. David Fifield (Jan 18)
- Re: nmap crash -- NmapOutputTable.cc:153: void NmapOutputTable::addItem(unsigned int, unsigned int, bool, const char*, int): Assertion `row < numRows' failed. Jon Kibler (Jan 18)