Nmap Development mailing list archives
Re: nmap: nsock_core.c:294: handle_connect_result: Assertion `0' failed.
From: Fyodor <fyodor () insecure org>
Date: Thu, 14 May 2009 20:01:06 -0700
On Wed, May 13, 2009 at 09:33:01AM +0200, Fabio wrote:
/* These match the SunOS error numbering scheme. */ Can you try the same patch as before, this time using ENOPROTOOPT instead of ENOMSG?OK, ENOPROTOOPT works for both SPARC and x86, while ENOMSG works only on x86.
Thanks for testing, Fabio. I've checked in David's patch with the substitution of ENOPROTOOPT for ENOMSG. Cheers, -F _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Re: nmap: nsock_core.c:294: handle_connect_result: Assertion `0' failed. Fabio (Apr 30)
- Re: nmap: nsock_core.c:294: handle_connect_result: Assertion `0' failed. David Fifield (Apr 30)
- <Possible follow-ups>
- Re: nmap: nsock_core.c:294: handle_connect_result: Assertion `0' failed. Fabio (May 04)
- Re: nmap: nsock_core.c:294: handle_connect_result: Assertion `0' failed. David Fifield (May 12)
- Re: nmap: nsock_core.c:294: handle_connect_result: Assertion `0' failed. Fabio (May 13)
- Re: nmap: nsock_core.c:294: handle_connect_result: Assertion `0' failed. Fyodor (May 14)
