[klibc] Problems with fread

H. Peter Anvin hpa at zytor.com
Tue Feb 7 21:51:59 PST 2006

Martin Schlemmer wrote:
> Well, since you have to check line for line, and klibc did not provide
> fscanf() which was originally used, I used fread+sscanf and reading one
> byte at a time into a 300 byte buffer.

What kernel version is this?  This could be a seq_file bug.  It's 
clearly the kernel that's at fault, though.

fscanf/fgets is part of the reason I'm thinking of at least adding input 
buffering to klibc, as annoying as it is...


More information about the klibc mailing list