From owner-freebsd-stable@FreeBSD.ORG Sat Oct 17 22:04:55 2009 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19A3C1065670 for ; Sat, 17 Oct 2009 22:04:55 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.freebsd.org (Postfix) with ESMTP id 18DF58FC1F for ; Sat, 17 Oct 2009 22:04:53 +0000 (UTC) Received: from aldan.algebra.com (localhost [127.0.0.1]) by aldan.algebra.com (8.14.3/8.14.3) with ESMTP id n9HM4kWp022057; Sat, 17 Oct 2009 18:04:49 -0400 (EDT) (envelope-from mi+thun@aldan.algebra.com) Message-ID: <4ADA3F7E.1070208@aldan.algebra.com> Date: Sat, 17 Oct 2009 18:04:46 -0400 From: "Mikhail T." User-Agent: Thunderbird 2.0.0.22 (X11/20090711) MIME-Version: 1.0 To: Kostik Belousov References: <4AD9F4ED.2050002@aldan.algebra.com> <20091017172718.GJ2160@deviant.kiev.zoral.com.ua> <4ADA04B3.1000704@aldan.algebra.com> <20091017175941.GK2160@deviant.kiev.zoral.com.ua> In-Reply-To: <20091017175941.GK2160@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit Cc: stable@freebsd.org Subject: Re: Can close-ing a pipe trigger a SIGPIPE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Oct 2009 22:04:55 -0000 Kostik Belousov ΞΑΠΙΣΑΧ(ΜΑ): >> This 0-size write must be part of the pipe-closing -- descriptors 4 and >> 5 must be the pipe's: >> >> 92722 tclsh8.5 CALL write(0x4,0x800e24028,0) >> 92722 tclsh8.5 RET write -1 errno 32 Broken pipe >> 92722 tclsh8.5 PSIG SIGPIPE caught handler=0x800f126d0 mask=0x0 code=0x0 >> 92722 tclsh8.5 CALL sigreturn(0x7fffffffa0c0) >> 92722 tclsh8.5 RET sigreturn JUSTRETURN >> 92722 tclsh8.5 CALL close(0x5) >> 92722 tclsh8.5 RET close 0 >> 92722 tclsh8.5 CALL close(0x4) >> 92722 tclsh8.5 RET close 0 >> >> Why would it write 0 bytes? Is doing so triggering a SIGPIPE now -- but, >> perhaps, didn't use to? >> > > Obviously, I cannot answer the question. This is something that should > be read from source code or asked by authors. > You -- or someone else -- could comment like: a) Yeah, the meaning of write-ing 0 bytes changed in version such and such to conform to such and such standard. or b) No, nothing changed in that area of FreeBSD for years -- there must be something in Tcl itself. Yours, -mi