Re: Bug in Parallel DNS resolution in Nmap 4.50?

[Lionel Cons <lionel.cons () cern ch>]

doug () hcsw org writes:
> Thanks for doing this! Hm.. You ran it for a couple
> minutes and the last output was timestamped at about
> 4 seconds or so and it is in a busy loop? Very strange.

FWIW, I could reproduce it today with the latest Nmap from SVN.

> What might help a lot is a backtrace. If you have GDB
> avaiable could you please try this:

Here is what I get:

Program received signal SIGINT, Interrupt.
0x080a3987 in nmap_mass_rdns ()
(gdb) bt
#0  0x080a3987 in nmap_mass_rdns ()
#1  0x080a3f6d in nmap_mass_rdns ()
#2  0x080c0026 in msevent_dispatch_and_delete ()
#3  0x080bdef9 in nsock_loop ()
#4  0x080a342f in nmap_mass_rdns ()
#5  0x0806594f in nexthost ()
#6  0x08060b62 in nmap_main ()
#7  0x0805c6d9 in main ()

> Because yours is busy looping, it probably will not
> have a select() call as the top stack frame and this 
> location might help track the bug down.

Indeed.

Please let me know if you need further help to track this bug down.

Cheers,

Lionel

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