Re: Assertion failed during output of an NSE script

["Eddie Bell" <ejlbell () gmail com>]

I have recently made some changes to NmapOutputTable but if the error
was present in the main trunk it couldn't have been that. Could you
send the script you were using when the error occurred?

On 11/06/07, Thomas Buchanan <TBuchanan () thecompassgrp net> wrote:
> I was doing some testing on another NSE script I'm working on, and ran
> into the following error message, which results in an early termination
> of the running nmap process.  It seems to be repeatable on my system,
> but I really don't know what steps I should take to try to track it
> down.  Maybe somebody can give me some pointers.
>
> Here's the error message:
>
> nmap: NmapOutputTable.cc:162: void NmapOutputTable::addItem(unsigned
> int, unsigned int, bool, const char*, int): Assertion `row < numRows'
> failed.
>
> The error message only seems to occur when nmap only displays
> "Interesting ports", but does not occur when the output for each port is
> listed (this seems to happen when ~20 or fewer ports are scanned).
>
> I get the same error message with the main nmap SVN branch and the soc07
> SVN branch.
>
> I can provide more detailed output if needed.  Let me know if anything
> else needs clarification.
>
> Thanks,
>
> Thomas
>
> ps.  Here's a complete copy of the output:
>
> Starting Nmap 4.21ALPHA5 ( http://insecure.org ) at 2007-06-11 15:27 CDT
> Initiating ARP Ping Scan at 15:27
> Scanning 192.168.xx.yy [1 port]
> Completed ARP Ping Scan at 15:27, 0.23s elapsed (1 total hosts)
> Initiating Parallel DNS resolution of 1 host. at 15:27
> Completed Parallel DNS resolution of 1 host. at 15:27, 0.00s elapsed
> Initiating UDP Scan at 15:27
> Scanning 192.168.xx.yy [31 ports]
> Completed UDP Scan at 15:27, 3.67s elapsed (31 total ports)
> SCRIPT ENGINE: Initiating script scanning.
> Initiating SCRIPT ENGINE at 15:27
> nmap: NmapOutputTable.cc:162: void NmapOutputTable::addItem(unsigned
> int, unsigned int, bool, const char*, int): Assertion `row < numRows'
> failed.
> Host 192.168.xx.yy appears to be up ... good.
> Interesting ports on 192.168.xx.yy:
> Not shown: 30 open|filtered ports
> <---------------------------------
> End of nmap output
>
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://SecLists.Org

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