This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients neologix, pitrou, serhiy.storchaka, vstinner
Date 2015-03-09.15:43:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1425915804.92.0.124670076416.issue23618@psf.upfronthosting.co.za>
In-reply-to
Content
> http://www.madore.org/~david/computers/connect-intr.html

This article contains a program connect_test.c to test how connect() behaves on EINTR. Since it's in the public domain, I attached a copy.

The program contains the comment: "All systems function as expected when TEST_TWO is set."

If TEST_TWO is defined, poll() is used to wait until the socket is writable, and then getsockopt(SO_ERROR) is used to check if the error is now zero, when connect() fails with EINTR.
History
Date User Action Args
2015-03-09 15:43:24vstinnersetrecipients: + vstinner, pitrou, neologix, serhiy.storchaka
2015-03-09 15:43:24vstinnersetmessageid: <1425915804.92.0.124670076416.issue23618@psf.upfronthosting.co.za>
2015-03-09 15:43:24vstinnerlinkissue23618 messages
2015-03-09 15:43:24vstinnercreate