From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <9AD200D3-04A5-409F-949C-3F36DA5EA0CD@corpus-callosum.com> References: <9AD200D3-04A5-409F-949C-3F36DA5EA0CD@corpus-callosum.com> Date: Thu, 28 Feb 2013 23:13:10 +0000 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7bf19844c13bc804d6d10875 Subject: Re: [9fans] X11 [was APE select and awkward Python subprocess PIPEfitting] Topicbox-Message-UUID: 2111f100-ead8-11e9-9d60-3106f5b1d025 --047d7bf19844c13bc804d6d10875 Content-Type: text/plain; charset=UTF-8 On 28 February 2013 23:02, Jeff Sickel wrote: > that just removes the > offending EBADF > it should generate EBADF for any bit set in any of the fd_sets when that bit doesn't correspond to an open file descriptor. the mistake was producing EBADF on a very specific condition associated with an *open* file descriptor --047d7bf19844c13bc804d6d10875 Content-Type: text/html; charset=UTF-8

On 28 February 2013 23:02, Jeff Sickel <jas@corpus-callosum.com> wrote:
that just removes the
offending EBADF

it should generate EBADF for any bit set in any of the fd_sets when that bit doesn't correspond to an open file descriptor.
the mistake was producing EBADF on a very specific condition associated with an *open* file descriptor
--047d7bf19844c13bc804d6d10875--