Re: Weird Crash - "WAITING_TO_RUNNING"

[David Fifield <david () bamsoftware com>]

On Mon, Nov 22, 2010 at 04:42:45PM -0800, David Fifield wrote:
> On Mon, Nov 22, 2010 at 05:37:54PM -0700, Nathan wrote:
> > On Mon, Nov 22, 2010 at 5:11 PM, David Fifield <david () bamsoftware com> wrote:
> > > > > If you consistently get different results over, say, three runs, then
> > > > > I'll look at it closer.
> > > >
> > > > Sure thing.  It looks pretty consistent to me.  Here's three runs on
> > > > the same server with 5.35DC1 with your custom nse_main.lua:
> > > >
> > > > Scan ending at Mon Nov 22 16:45:14 MST 2010:
> > > > 5m12s - 53392KB RAM
> > > >
> > > > Scan ending at Mon Nov 22 16:51:06 MST 2010:
> > > > 5m8s - 54836KB RAM
> > > >
> > > > Scan ending at Mon Nov 22 16:58:16 MST 2010
> > > > 5m26s - 55980KB RAM
> > > >
> > > > (Note that I didn't run these end-on-end, I typed some stuff into this
> > > > email in between each scan)
> > >
> > > And if you're still available, can you do one more with 5.36TEST2?
> > >
> > > David Fifield
> >
> > 5.36TEST2 with CONCURRENCY_LIMIT lowered to 100:
> > Scan ending at Mon Nov 22 17:29:20 MST 2010
> > 13m26 - 69644KB RAM
> >
> > I've got to run -- I'm late leaving work, but I can rerun it without
> > the altered CONCURRENCY_LIMIT tomorrow (I forgot I had that alteration
> > in there).
>
> That's fine; I think this is conclusive enough.

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 Fifield

Attachment: nse_main.lua.1
Description:

Attachment: nse_main.lua.2
Description:

Attachment: nse_main.lua.3
Description:

Attachment: nse_main.lua.4
Description:

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