Nmap Development mailing list archives

Re: Nmap 5.50 crashing: Assertion `timeout_msecs >= 0' failed


From: David Fifield <david () bamsoftware com>
Date: Tue, 1 Feb 2011 13:21:04 -0800

On Mon, Jan 31, 2011 at 11:49:11PM +0100, Vlatko Kosturjak wrote:
On 01/31/2011 05:58 PM, David Fifield wrote:
On Mon, Jan 31, 2011 at 12:36:33PM +0100, Vlatko Kosturjak wrote:
Please try with this patch. It will do a controlled Lua error so we see
a stack trace and find out which script is responsible. For example,

NSE: 'path-mtu' (thread: 0x99555c0) against 192.168.0.2 threw an error!
./scripts/path-mtu.nse:320: NEGATIVE TIMEOUT: -150
stack traceback:
        [C]: in function 'set_timeout'
        ./scripts/path-mtu.nse:320: in function <./scripts/path-mtu.nse:295>
        (tail call): ?

The fact that a script can halt Nmap in this way is another bug, but
let's first fix whatever script is setting a negative timeout.

Unfortunately, tried with exactly same command line and with exactly
same target IPs two times, but cannot reproduce any more :(

Okay, no big deal. I committed the patch so it at least won't be a fatal
error in the future.

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: