|
Nmap Hackers
mailing list archives
Re: Re: -O SIGSEGV
From: Karl Boehnker <boehnker () hoare cs umsl edu>
Date: Wed, 16 Dec 1998 18:24:23 -0600 (CST)
On Wed, 16 Dec 1998, HD Moore wrote:
Im still finding new ways to cause SIGSEGV's just by not adding any
arguments to -p, -O, a few others.. Maybe I will spend an hour finding
them
all and organizing it..
It crashes when you start doing the OS detection (e.g. after ping and
portscan) or before?
use -dd -vv and dump the error msgs....
After the ping & portscan. Nothing on stderr except for the "caught
SIGSEGV...". In my dwindling spare time I'm looking into it as well.
------ snip ---------
For OSScan assuming that port 7 is open and port 37424 is closed and
neither are firewalled
Got packet for test number 1
Got packet for test number 4
Got packet for test number 5
Got packet for test number 6
Got packet for test number 7
caught SIGSEGV signal, cleaning up
Aborted
By Date
By Thread
Current thread:
- -O SIGSEGV Karl Boehnker (Dec 16)
- <Possible follow-ups>
- Re: -O SIGSEGV HD Moore (Dec 16)
- Re: Re: -O SIGSEGV Karl Boehnker (Dec 16)
|