Aloha -
I've seen this behavior several times with Hurd: fprintf(stderr, ...) will
return -1 with errno = EINTR.
I'm not used to fprintf failing like this (I'm getting used to it), and
this last time I spent several hours hunting for a "bug" that turned out to
be nothing more than a debugging statement failing to print.
Is this a bug? (I suppose fprintf to stderr could fail...) Have others
seen this behavior?
I have a test program that reproduces it consistently. Should I file it as
a bug report?
agape
brent
