Nmap Development mailing list archives

Re: SIGSEGV signal on Darwin OS X (Intel) when using version matching (nmap 4.01)


From: "Kelly M" <bangpath () sent as>
Date: Sun, 05 Mar 2006 23:25:59 -0500

On Sun, 5 Mar 2006 23:01:43 -0500, "David Warde-Farley"
<david.warde.farley () utoronto ca> said:
Try this at the command line:

gdb nmap

When you're at the gdb prompt, type "run" followed by a space and  
then the arguments you were passing to nmap when the crash happened.

Finally, when it segfaults, type "bt" to get a stack trace. Paste  
that here. You can quit gdb with 'q'.

Thanks for walking me through that. Here's the output I got:

(gdb) run -sS -T4 -A 111.222.333.444
Starting program: /usr/local/bin/nmap -sS -T4 -A 111.222.333.444
Reading symbols for shared libraries . done

Starting Nmap 4.01 ( http://www.insecure.org/nmap/ ) at 2006-03-05 23:12
EST

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0xc0000000
0x0004486d in ?? ()
(gdb) bt
#0  0x0004486d in ?? ()
#1  0x00000000 in ?? ()
Previous frame inner to this frame (corrupt stack?)


Kelly


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


Current thread: