-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
piping to a screen pager (e.g. less(1) or more(1)) blocks program #2
Comments
@bxparks please see my pull request |
Explicitly set O_NONBLOCK to stdin while running tests #2
@mmrazik: Let's transfer the discussion from #24 to here. The number of lines needed to trigger the error seems to be variable. Changes across machine and OS, sometimes different on the same machine. I checked in a version of
|
I believe I have finally fixed this with bf6248f. |
As noted in the README.md, if the executable (e.g.
SampleTest.out
) is piped to a screen pager likeless(1)
ormore(1)
, sometimes (not all the time) the executable hangs and displays nothing on the pager program. The program seems to be blocking on the standard input. The problem is probably caused by an interaction between how the screen pager manipulates thestdin
and how I place the stdin into "raw" mode inArduino.cpp
. I would love to fix this, but I don't know enough about Unix tty device configuration to figure this out.In the meantime, the workaround is to explicitly redirect the
stdin
using/dev/null
, like this:The text was updated successfully, but these errors were encountered: