Re: nmap: nsock_event.c:406: msevent_new: Assertion `msiod->state != NSIOD_STATE_DELETED' failed

["Luis MartinGarcia." <luis.mgarc () gmail com>]

On 11/21/2012 10:35 PM, David Fifield wrote:
> On Wed, Nov 21, 2012 at 09:34:02AM +0100, Henri Doreau wrote:
> > 2012/11/21 David Fifield <david () bamsoftware com>:
> > > I think this is a separate issue.
> > >
> > > Could you try changing NSOCK_TRACE_LEVEL in nmap.h to 9, and running
> > > with the -d3 option? This will create a ton of output, perhaps including
> > > the immediate cause of why you're seeing this error message.
> > >
> > > David Fifield
> > Small thread hijack, as we're talking about a debug patch to get nsock
> > logs: What about always (i.e.: nmap, nping, ncat) applying the
> > application's debug level to nsock? This would eliminate the need for
> > such debugging patches. It would indeed be verbose, but that's what
> > users expect anyway when enabling a debug mode I guess.
> That's cool. There should be a function that maps Nmap, etc. debug level
> into Nsock trace levels. Nmap -d1 may not translate directly into Nsock
> trace level 1, for example.

Hi,

Nping already does this. In ProbeEngine.cc there is this:

    /* Set nsock trace level */
    gettimeofday(&now, NULL);
    if( o.getDebugging() == DBG_5)
      nsp_settrace(nsp, NULL, 1 , &now);
    else if( o.getDebugging() > DBG_5 )
      nsp_settrace(nsp, NULL, 10 , &now);

Just my two cents.

Regards,

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