Mailinglist Archive: opensuse-programming (33 mails)
| < Previous | Next > |
Re: [suse-programming-e] EAGAIN on a blocking socket?
- From: Per Jessen <per@xxxxxxxxxxxx>
- Date: Thu, 02 Mar 2006 20:44:37 +0100
- Message-id: <du7hv5$kmv$2@xxxxxxxxxxxxxxxx>
Anders Johansson wrote:
>> I think I removed it again. I basically did a check just before
>> fputs(). Something like this:
>>
>> fcntl( fd, F_GETFL, &flag );
>> if ( flag & O_NONBLOCK ) log_error("nonblocking when it shudnt be");
>
> and you're saying you never saw this error message in the log? That is
> strange, that would definitely be worth a bug report. If you could
> write a minimal program that exhibits the problem, and include the
> glibc version and kernel you use, I don't think it would take the
> developers long to fix
I'll now be double- and triple-checking it, but I'm fairly certain
that's the behaviour I saw.
Thanks for your time guys - I knew a third and fourth pair of eyes would
come in handy.
/Per Jessen, Zürich
>> I think I removed it again. I basically did a check just before
>> fputs(). Something like this:
>>
>> fcntl( fd, F_GETFL, &flag );
>> if ( flag & O_NONBLOCK ) log_error("nonblocking when it shudnt be");
>
> and you're saying you never saw this error message in the log? That is
> strange, that would definitely be worth a bug report. If you could
> write a minimal program that exhibits the problem, and include the
> glibc version and kernel you use, I don't think it would take the
> developers long to fix
I'll now be double- and triple-checking it, but I'm fairly certain
that's the behaviour I saw.
Thanks for your time guys - I knew a third and fourth pair of eyes would
come in handy.
/Per Jessen, Zürich
| < Previous | Next > |