On Friday, 11 December 2020 at 18:18:35 UTC, kdevel wrote:
On Friday, 11 December 2020 at 16:49:18 UTC, Adam D. Ruppe
wrote:
libc-2.30.so
The bug was fixed in 2.28 IIRC.
so i guess i have the fixed libc. Can you confirm what version
you have?
Various. I tested the code on a machine running the yet EOL
CENTOS-6
having glibc 2.12.
Of course that could be "your" bug.
But you should test your program with another stream than stdin
to ensure the terminal is not the problem because read(2) is
lowlevel and you may not see where it really comes from. Maybe
the terminal checks again or there are some buffers between
terminal and your program.
