Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.11) Gecko/20050728 MultiZilla/1.7.0.1j
Strange to me that is.
Why am I asking here? Perhaps I should make a fool of myself to the
kernel or glibc people?
Well I know geniuses hang out here. Plus coreutils must have dealt with
issues like this if it is indeed normal.
$ ls -la fread-fseek.c
-rw-r--r-- 1 joe joe 1155 Jan 26 13:37 fread-fseek.c
$ cat fread-fseek.c | wc -l
56
$ cat fread-fseek.c | while ./fread-fseek 1156; do true ; done | wc -l
1
$ cat fread-fseek.c | while ./fread-fseek 1155; do true ; done | wc -l
1
$ cat fread-fseek.c | while ./fread-fseek 1; do true ; done | wc -l
1
$ while ./fread-fseek 1156; do true ; done < fread-fseek.c | wc -l
56
$ while ./fread-fseek 1155; do true ; done < fread-fseek.c | wc -l
1
$ while ./fread-fseek 1; do true ; done < fread-fseek.c | wc -l
1
where the numeric arg is the number of bytes that fread should read per
call.
Strace shows reads are done in 4096 and _llseek calls look strange.
here is an example
read(0, "#include <stdio.h>\n#include <lib"..., 4096) = 1155
fstat64(1, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
_llseek(0, 1155, [1155], SEEK_SET) = 0
write(1, "#include <stdio.h>\n", 19#include <stdio.h>
and this is the one where things perform as expected
read(0, "#include <stdio.h>\n#include <lib"..., 4096) = 1155
read(0, "", 4096) = 0
fstat64(1, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0