Date: Sat, 17 Oct 2009 18:04:46 -0400 From: "Mikhail T." <mi+thun@aldan.algebra.com> To: Kostik Belousov <kostikbel@gmail.com> Cc: stable@freebsd.org Subject: Re: Can close-ing a pipe trigger a SIGPIPE? Message-ID: <4ADA3F7E.1070208@aldan.algebra.com> In-Reply-To: <20091017175941.GK2160@deviant.kiev.zoral.com.ua> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ADA3F7E.1070208>