Nmap Development mailing list archives
Re: Weird Crash - "WAITING_TO_RUNNING"
From: David Fifield <david () bamsoftware com>
Date: Fri, 3 Dec 2010 16:49:41 -0800
On Fri, Dec 03, 2010 at 11:17:49AM -0700, Nathan wrote:
On Tue, Nov 23, 2010 at 2:59 PM, David Fifield <david () bamsoftware com> wrote:I looked over the code and I can't find what might be causing the change in run time. I attached four different versions of nse_main.lua that make incremental changes. Please try running each of the four and report the times you get. Just copy each one over nse_main.lua in turn. David FifieldSorry for the delay, it's been a very busy work week. Here are the measurements you asked for with your custom versions of nse_main.lua. Please note that the values will fluctuate ~2% from run to run, but within about that margin of error the runs were very consistent with themselves. Also, these were all run with nmap 5.35DC1, with nse_main.lua replaced by the file indicated. nse_main.lua.1: 53732 kB RAM, 5m40s nse_main.lua.2: 53588 kB RAM, 5m21s nse_main.lua.3: 55512 kB RAM, 5m27s nse_main.lua.4: 54352 kB RAM, 5m22s Since none of those seem to display any problems, I went and ran a bunch of other things: 1) Here's the nse_main.lua pulled from 5.36TEST2 and copied over into 5.35DC1 54448 kB RAM, 5m23s 2) Same as #1, but with the CONCURRENCY_LIMIT lowered to 100 54312 kB RAM, 5m32.126s 3) Here's the vanilla nmap 5.36TEST2 on the same machine (when I run this one, I compile it but don't install it, then I run it from the directory it was compiled in). 94532 kB RAM, 14m48s
When you are running from the same directory, do you use "--datadir ."? If not, it might be referring to the wrong nse_main.lua (the installed one). Try your command with nmap --datadir . <args..>
So what really mystifies me is #1 up there. It's the nse_main.lua from 5.36TEST2 with a CONCURRENCY_LIMIT of 1000, and yet it seems to run fine. And then that same file running under nmap 5.36TEST2 performs horribly. Perhaps the problem is with some other change in 5.36TEST2, and not in nse_main.lua. Please let me know if you would like me to try anything else out.
I looked through the logs and identified revisions that are more likely to have changed something in NSE betweern 5.35DC1 and 5.36TEST1. I know this is asking a lot, but if the --datadir doesn't solve it, please try building and testing each of these revisions: 19514 19515 20266 20267 20632 20633 Starting from a Subversion checkout, you will run svn update --ignore-externals -r 19514 . nbase ncat nping nsock zenmap Then build and test, using "--datadir .". Then move on to 19515, 20266, etc. (You don't have to check out again every time.) 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:
- Re: Weird Crash - "WAITING_TO_RUNNING", (continued)
- Re: Weird Crash - "WAITING_TO_RUNNING" Nathan (Nov 15)
- Re: Weird Crash - "WAITING_TO_RUNNING" David Fifield (Nov 17)
- Re: Weird Crash - "WAITING_TO_RUNNING" Nathan (Nov 22)
- Re: Weird Crash - "WAITING_TO_RUNNING" David Fifield (Nov 22)
- Re: Weird Crash - "WAITING_TO_RUNNING" Nathan (Nov 22)
- Re: Weird Crash - "WAITING_TO_RUNNING" David Fifield (Nov 22)
- Re: Weird Crash - "WAITING_TO_RUNNING" Nathan (Nov 22)
- Re: Weird Crash - "WAITING_TO_RUNNING" David Fifield (Nov 22)
- Re: Weird Crash - "WAITING_TO_RUNNING" David Fifield (Nov 26)
- Re: Weird Crash - "WAITING_TO_RUNNING" Nathan (Dec 03)
- Re: Weird Crash - "WAITING_TO_RUNNING" David Fifield (Dec 03)
- Re: Weird Crash - "WAITING_TO_RUNNING" David Fifield (Dec 29)
- Re: Weird Crash - "WAITING_TO_RUNNING" Patrick Donnelly (Dec 13)
- Re: Weird Crash - "WAITING_TO_RUNNING" Nathan (Nov 08)