[konsole] [Bug 372991] Terminal gets stuck on interrupting a program that is outputting, preventing further output from being shown

[Egmont Koblinger]

https://bugs.kde.org/show_bug.cgi?id=372991

--- Comment #9 from Egmont Koblinger <egmont at gmail.com> ---
Without having looked at the code, I'm wondering how FIONREAD can return 0... I
mean I guess it's preceded by a select() or similar that waits for data to
appear, and the reason for reaching FIONREAD is that it signaled some data
available. But maybe this is where somehow (how?) multithreaded race
condition-y stuff kicks in.

As far as I know, terminal devices don't have the concept of EOF, 0 should mean
"oops someone just grabbed that data before us". (There's a concept of EOF, as
in "stty eof" in the other part, from the keyboard to the kernel driver.)

-- 
You are receiving this mail because:
You are the assignee for the bug.