Nmap Development mailing list archives
nsock_core.c:293 assertion failure (EPIPE, pipe broken)
From: Brandon Enright <bmenrigh () ucsd edu>
Date: Fri, 27 Feb 2009 02:00:48 +0000
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fellow developers, While testing with David some NSE related problems, I got Nmap to crash with the following error: ...NSE output... Strange connect error from x.y.26.133 (32): Success nmap: nsock_core.c:293: handle_connect_result: Assertion `0' failed. I was running Nmap in Valgrind at the time although no interesting output was produce and I don't think Valgrind was the issue. One rather perplexing thing about this assertion failure was that no coredump was produced. I confirmed that my shell was set to "ulimit -c unlimited". assert() normally calls abort(). David did some searching and there is mention of EPIPE being returned on send() calls when the remote host closes the connection unexpectedly. The Nsock output though seems to indicate that EPIPE was broken during a connect() If anyone has any ideas on this one David and I would be most interested in hearing them. Brandon -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmnSVYACgkQqaGPzAsl94J6tACguXb/Ux46p/47Xrtk5XdMFV8+ sxEAoJ/xPAauYNYbLTgSY55/qp5Ls5nJ =02B4 -----END PGP SIGNATURE----- _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- nsock_core.c:293 assertion failure (EPIPE, pipe broken) Brandon Enright (Feb 26)
- Re: nsock_core.c:293 assertion failure (EPIPE, pipe broken) doug (Feb 26)
- Re: nsock_core.c:293 assertion failure (EPIPE, pipe broken) Brandon Enright (Feb 26)
- Re: nsock_core.c:293 assertion failure (EPIPE, pipe broken) doug (Feb 26)