-
Notifications
You must be signed in to change notification settings - Fork 534
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
Handle select errors. #64
Comments
Sorry for the inconvenience! At least EINTR really has to be caught. The issue should be fixed in the unstable branch (see the related commit), so you can hopefully go on using libcppa by switching to do the unstable branch until 0.4.2 releases. After the patch, the middleman is calling exit only for really serious errors like invalid error codes or integer overflows on socket descriptors. |
Thanks a lot! 28.08.2012 22:19 ÐÏÌØÚÏ×ÁÔÅÌØ "Dominik Charousset" notifications@github.com Sorry for the inconvenience! At least EINTR really has to be caught. The Reply to this email directly or view it on |
Just for the record: I experienced this bug as well when facing high message loads. Thankfully it's resolved. |
I have found the hard way that libcppa calls
exit
from middleman.cpp:I think select errors should be handled gracefully and explained with "strerror".
(It's a blocker, I can't use libcppa as long as it calls exit instead of handling errros.
AFAIK, it is even normal for select to exit with EINTR).
The text was updated successfully, but these errors were encountered: