This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: XIO error... anyone seen it? [found and fixed]
On Fri, Nov 09, 2001 at 01:10:25AM +0100, Corinna Vinschen wrote:
>On Thu, Nov 08, 2001 at 06:43:50PM -0500, Christopher Faylor wrote:
>> On Thu, Nov 08, 2001 at 11:10:28PM +0000, Alan Hourihane wrote:
>> >On Thu, Nov 08, 2001 at 02:17:49PM -0800, Brian Genisio wrote:
>> >> Should we add the folowing line to XlibInt.c? :
>> >> #ifdef __CYGWIN__
>> >> #define ETEST() (errno == EAGAIN || errno == EWOULDBLOCK || errno == ENOBUFS)
>> >>
>> >> Or, is there a better solution? What do you (Cyg/XF86 developers) think?
>> >
>> >Seems like a reasonable assessment Brian. We could do this, although I'd
>> >like to understand why there isn't any buffer space on the socket.
>> >
>> >Is there a test application you can email to me for testing..?
>>
>> I wonder if cygwin should just be mapping WSAENOBUFS to EAGAIN. It seems like
>> we somehow invented a new errno here.
>
>No. ENOBUFS is a used and documented error code on Linux and SUSv2.
>E.g. `man 2 send' contains:
>
> ENOBUFS
> The output queue for a network interface was full.
> This generally indicates that the interface has
> stopped sending, but may be caused by transient
> congestion. (This cannot occur in Linux, packets
> are just silently dropped when a device queue over?
> flows.)
Oh, yes, right. I forgot that I can't just look in /usr/include/sys/errno.h
on linux if I want to find a define.
I think I need to write a "headergrep" utility. I know that it would be
really useful for searching for this kind of thing.
cgf