Re: [Exp PATCH] Start OSScan more quickly

Eddie Bell wrote:
> Hey Kris,
>
> Cool idea. I haven't look at the code very deeply but I think
> clearHost() causes problems for the code that runs after it
>
> $ sudo gdb ./nmap
> (gdb) r -sS -p1-30 -O --osscan-quick -iR 200 -v
>
> <snip>
>
> Program received signal SIGSEGV, Segmentation fault.
> HostScanStats::destroyOutstandingProbe at scan_engine.cc:1501
> 1501 if (!probe->timedout) {
> (gdb) info stack
> #0 HostScanStats::destroyOutstandingProbe (this=0xf859a0,
> probeI=<value optimized out>) at scan_engine.cc:1501
> #1 0x000000000043474f in HostScanStats::clearHost (this=0xf859a0) at
> scan_engine.cc:1483
> #2 0x000000000043966d in processData (USI=0xf857a0) at scan_engine.cc:3389
>
> Also the check in scan_engine.cc only checks for osscan_quick. This
> might cause a problem if the user has only specified that and not an
> osscan (-O)
>
> cheers
> - eddie
>

Hey Eddie, thanks for testing!

I have attached a patch with some simple changes to fix the problems you
mentioned (they worked for me).

Please let me know if you have any more problems! :)

Thanks,
Kris Katterjohn

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