https://bugs.kde.org/show_bug.cgi?id=452274
--- Comment #20 from Nick Briggs <afraid-splicer...@icloud.com> ---
I'm not sure why the write() would be flagged non-blocking.
You can replace the write(...) in the test with read(0, NULL, 0) and get the
same result.
I also tried
int fd = open("/tmp/dummy", O_WRONLY, O_CREAT);
if (fd != -1) close(fd);
and got the failure. I wonder if it's possible that it fails with any of the
syscalls that are in the list in sigaction's SA_RESTART (although actually
*using* SA_RESTART doesn't seem to affect the test case)
%%%%%
The affected system calls include open(2), read(2), write(2),
sendto(2), recvfrom(2), sendmsg(2) and recvmsg(2) on a communications
channel or a slow device (such as a terminal, but not a regular file) and
during a wait(2) or ioctl(2). However, calls that have already committed
are not restarted, but instead return a partial success (for example, a
short read count).
%%%%%
I've made it fail with read(), write(), open(), wait(), but neither stat() nor
usleep().
--
You are receiving this mail because:
You are watching all bug changes.
