Nmap Development mailing list archives

Re: Scripting engine stuck


From: Ron <ronlists () skullsecurity com>
Date: Mon, 03 Dec 2007 15:15:39 -0600

bash-3.1$ sudo nmap -vvv -sS -O -sV --script=all -oX test2.xml 
--script-trace XXX.YYY.ZZZ.0/24 > stdout.txt
Password:
WARNING:  OS didn't match until try #2
Segmentation fault


Attached stdout output (for real this time!)

I'm going to try removing options until it stops blowing up. I'll let 
you know when I find more info, but stop me if this is something that's 
already fixed.

I could swear I sent this already this morning, but it doesn't seem to 
be on the list. But it's money, the power was out for an hour, and I've 
been eating chocolate all day, so I don't know what's going on.

Here's a backtrace of it crashing:
-----
(gdb) run -vvv --script=all -oX ~/test2.xml --script-trace 
XXX.YYY.ZZZ.0/24 > ~/stdout.txt
Starting program: /home/ron/downloads/nmap-4.23RC3/nmap

Program received signal SIGSEGV, Segmentation fault.
0x080bd056 in msevent_new (nsp=0x82f9310, type=1284, msiod=0x0,
     timeout_msecs=457500, handler=0, userdata=0x0) at nsock_event.c:383
383             nsock_trace(nsp, "msevent_new (IOD #%li) (EID #%li)",
Current language:  auto; currently c
(gdb) backtrace
#0  0x080bd056 in msevent_new (nsp=0x82f9310, type=1284, msiod=0x0,
     timeout_msecs=457500, handler=0, userdata=0x0) at nsock_event.c:383
#1  0x080bc592 in nsock_timer_create (ms_pool=0x82f9310,
     handler=0x80ab510 <l_nsock_connect_queued_handler(void*, void*, 
void*)>,
     timeout_msecs=0, userdata=0x83d4dc8) at nsock_timers.c:67
#2  0x080ac5f8 in l_nsock_close (l=0x83d4030) at nse_nsock.cc:586
#3  0x080d4db6 in luaD_precall ()
#4  0x080dd92c in luaV_execute ()
#5  0x080d463e in luaD_rawrunprotected ()
#6  0x080d52d8 in lua_resume ()
#7  0x080a8573 in process_mainloop (l=0x82a27e8) at nse_main.cc:271
#8  0x080a971b in script_scan (targets=@0xbfffc1d0) at nse_main.cc:213
#9  0x08060d87 in nmap_main (argc=7, argv=0xbffff4e4) at nmap.cc:1752
#10 0x0805c41c in main (argc=7, argv=0xbffff4e4) at main.cc:227
-----

I can reproduce this easily, so if there's any other gdb commands that 
would help, let me know and I'll run them.

Hope that helps, and hope I didn't already send this,
Ron

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


Current thread: