From: Brett van de Sande <bvds@as...> - 2009-04-07 18:19:06
I am getting a "couldn't check whether ~S is readable: Bad file descriptor"
error. I am using sbcl 1.0.23 running CentOS on Intel, Linux version
The nearest I can tell is that this error occurs when some other process
in the OS is reading a large file at the same time. It doesn't occur
It is reapeatable: if I run my sbcl program and the other process
at the same time, I get this error. If I run my sbcl program and the
other process at the same time, with the other process reading
a smaller file, I don't get any error.
Brett van de Sande
On Tue, Apr 07, 2009 at 11:49:09AM -0700, Brett van de Sande wrote:
> >It's not quite clear to me how it's repeatable. Do you get that
> >message when you start sbcl? Do you get it when running a particular
> >program, or function, or something?
> I am running a program in SBCL that reads a file. The error occurs
> during that read attempt. The error only occurs when another
> (non-sbcl) program is reading a different large file at the same time.
> If I start both programs at the same time, the error is repeatable.
> If the other (non-sbcl) program is reading a different small file,
> I don't get any error.
> Also, the the SBCL program is running an third program via
> sb-ext:run-program with :input :stream :output :stream.
> If I turn this off, the "couldn't check whether ~S is readable"
> error goes away.
> Finally, the SBCL program reads lots of other files: 99%
> of the reads are successful.
> Sorry this is so complicated, but my attempts at further
> isolating the error have been unsuccessful.
It smells like serve-event to me, but I don't know much more than that.
> [how do I get this cc'ed back onto sbcl-devel?]
I've cc'd the list again, sorry.