Nmap Development mailing list archives
Re: --min-rate assertion failure
From: David Fifield <david () bamsoftware com>
Date: Thu, 24 Apr 2008 12:52:26 -0600
On Wed, Apr 23, 2008 at 01:00:12PM -0600, David Fifield wrote:
On Fri, Apr 18, 2008 at 08:58:16PM -0500, Kris Katterjohn wrote:I've run into a --min-rate assertion failure. Actually, it's not --min-rate specifically as I didn't use it, but the RateMeter stuff that is run regardless is the culprit. I've attached a file with the command used and all of the normal output from the scan.Thanks, Kris, I've verified and reproduced the bug. There's an integer overflow when subtracting two timevals, the one for the current time and the one for the time of the start of the scan. It happens after (1 << 31) / 1000000.0 / 60.0 ~= 35.79 minutes elapsed, which is why it showed up with a slow UDP scan.
I rewrote that part of the code to avoid the overflow and the assertion failure. Thanks for your report. David Fifield _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- --min-rate assertion failure Kris Katterjohn (Apr 18)
- Re: --min-rate assertion failure David Fifield (Apr 23)
- Re: --min-rate assertion failure David Fifield (Apr 24)
- Re: --min-rate assertion failure David Fifield (Apr 23)