Nmap Development mailing list archives

Re: Segfault in latest SVN


From: David Fifield <david () bamsoftware com>
Date: Wed, 18 Nov 2009 20:47:38 -0700

On Wed, Nov 18, 2009 at 07:21:10PM -0600, Ron wrote:
I'm not sure when this was introduced, and I'm currently on the clock
and can't troubleshoot, but here's the output:

ron@carrot:~/tools/nmap$ gdb ./nmap
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-slackware-linux"...
(gdb) run  -PN -p4567 -sV --script=http-* x.x.x.x
Starting program: /home/ron/tools/nmap/nmap -PN -p4567 -sV
--script=http-* x.x.x.x

Starting Nmap 5.05BETA1 ( http://nmap.org ) at 2009-11-04 14:13 EST

Program received signal SIGSEGV, Segmentation fault.
nsock_connect_tcp (nsp=0x83b8b38, ms_iod=0x0, handler=0x80b5cf0
<l_nsock_connect_handler(void*, void*, void*)>, timeout_msecs=10000,
userdata=0x8729308, saddr=0x871a6f8, sslen=16, port=4567)
    at nsock_connect.c:154
154       assert(nsi->state == NSIOD_STATE_INITIAL || nsi->state == NSIOD_STATE_UNKNOWN);

Thanks, Ron. I think this was caused by my r16121, which changed how NSE
sockets are created. I've reverted it until I can investigate.

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


Current thread: