You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug report refers to the latest perl found on Redhat 7.1 Intel Linux
systems.
The bug occurs when I try to read data from a CCD camera device driver
that I wrote. The driver returns 0 at end-of-file to signal that the image
has been completed, BUT if you then try to read again, it will return
EWOULDBLOCK since it assumes that you have re-opened the device and are
expecting a new image. The perl "read" function sometimes ignores the 0,
and appears to try reading from the device again.
Now, this is arguably a bug in my device driver (and I will fix it),
however, the fundamental point remains that the C "read" function returned
zero, indicating EOF, and the perl "read" function can ignore this. Perl
"read" seems to assume that if an EOF is returned once, then it should be
returned on subsequent reads.
Note that the perl "sysread" function works fine with my driver
(as do the usual UNIX utilities such as "cp" and "cat").
I hope that this bug report is useful. Sorry I didn't use "perlbug".
Migrated from rt.perl.org#7024 (status was 'open')
Searchable as RT7024$
The text was updated successfully, but these errors were encountered: