Re: No targets were specified error

[Jesper Kückelhahn <dev.kyckel () gmail com>]

Hi David,

Thanks for the reply.

I'm on a MacBook Pro with 10.8.2. I've just deleted my local copy of the svn, and checked out revision 30553. The 
problem is still the same. During 'make' I'm seeing a lot of 'is deprecated' warnings, though mainly in regards to 
OpenSSL.

I'll debug some more over the weekend.

- Jesper




On Jan 25, 2013, at 6:11 AM, David Fifield <david () bamsoftware com> wrote:

> On Thu, Jan 24, 2013 at 12:46:57AM +0100, Jesper Kückelhahn wrote:
> > After updating to an svn revision after 30538 I'm getting some strange
> > errors, that might to be related to the input arguments to nmap. If I
> > attempt to execute a basic nmap scan, I get a warning that no targets
> > were specified.
> >
> > $ nmap 192.168.1.20
> > WARNING: No targets were specified, so 0 hosts scanned.
> > Nmap done: 0 IP addresses (0 hosts up) scanned in 0.06 seconds 
> >
> > $ nmap -dd 192.168.1.20
> > Scanning 192.168.1.20 [2 ports]
> > Strange error from connect (22):Invalid argument
> > ultrascan_host_probe_update called for machine 192.168.1.20 state UNKNOWN -> HOST_DOWN (trynum 0 time: 73)
> > Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
> >
> > HomerMac:nmap kyckel$ nmap -ddd  192.168.1.20
> > Initiating Ping Scan at 00:39
> > Scanning 4096 hosts [2 ports/host]
> > CONN (0.0587s) TCP localhost > 0.5.1.5:80 => Invalid argument
> > Strange error from connect (22):Invalid argument
> > ultrascan_host_probe_update called for machine 0.5.1.5 state UNKNOWN -> HOST_DOWN (trynum 0 time: 91)
> > CONN (0.0588s) TCP localhost > 0.5.1.6:80 => Invalid argument
> > ultrascan_host_probe_update called for machine 0.5.1.6 state UNKNOWN -> HOST_DOWN (trynum 0 time: 19)
> > CONN (0.0588s) TCP localhost > 0.5.1.10:80 => Invalid argument
> > ultrascan_host_probe_update called for machine 0.5.1.10 state UNKNOWN -> HOST_DOWN (trynum 0 time: 16)
> > CONN (0.0588s) TCP localhost > 0.5.1.13:80 => Invalid argument
> > ultrascan_host_probe_update called for machine 0.5.1.13 state UNKNOWN -> HOST_DOWN (trynum 0 time: 15)
> > ultrascan_host_probe_update called for machine 0.5.1.125 state UNKNOWN -> HOST_DOWN (trynum 0 time: 15)
> > Moving 0.5.1.5 to completed hosts list with 0 outstanding probes.
> > Moving 0.5.1.6 to completed hosts list with 0 outstanding probes.
> > Moving 0.5.1.10 to completed hosts list with 0 outstanding probes.
> > Moving 0.5.1.13 to completed hosts list with 0 outstanding probes.
>
> This is very strange and looks like the use of uninitialized memory. I
> can't reproduce it on GNU/Linux. Does the problem remain after a "make
> clean" and "make"? What platform are you on?
>
> You can try running under Valgrind to see where a memory error is
> happening:
>       valgrind nmap -ddd 192.168.1.20
>
> David Fifield

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