https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27219
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
--- Comment #3 from mckinlay at redhat dot com 2006-04-20 21:45 ---
It does look like these should be made robust in the case of an EINTR which was
caused by a signal other than the interrupt signal.
As for ignoring ENOTCONN and ECONNRESET, I have a vague recollection that there
is a go
--- Comment #2 from tromey at gcc dot gnu dot org 2006-04-20 16:06 ---
Ignore that, I appended to the wrong report.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27219
--- Comment #1 from tromey at gcc dot gnu dot org 2006-04-20 15:54 ---
You can see it by compiling this short example
program with 'g++ --syntax-only':
#include
#include
--
tromey at gcc dot gnu dot org changed:
What|Removed |Added
-
