This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: XIO error... anyone seen it?
- To: Alan Hourihane <alanh at fairlite dot demon dot co dot uk>
- Subject: Re: XIO error... anyone seen it?
- From: Brian Genisio <briangenisio at yahoo dot com>
- Date: Mon, 5 Nov 2001 14:23:38 -0800 (PST)
- Cc: cygwin-xfree at cygwin dot com
Yes, I am running cygwin1.dll v 1.3.3.
I have been trying to debug the problem, and of course, running in a debugger
makes it much harder to find where the problem is. I think the fact that the
app runs slower in a debugger makes this buffer overrun problem no longer
happen. (Sucks for finding the problem, eh?)
In my application where I am having the most troubles, the
XpmCreatePixmapFromXpmImage function is where it crashes out. This function is
called many times in a row. I have tried a few things, with no improvement :
1. Call XFlush between calls
2. Call XSync between calls
3. Add a delay between calls.
This tells me that the problem is probably being caused by the
XpmCreatePixmapFromXpmImage itself. Some Pixmaps being loaded are as large as
2.6 MB (1280x960 in size) I hooked my app up to xmond, and found that the
following protocol calls were being made (for 59 XPM calls):
1 CreateWindow
4 InternAtom
1 GetProperty
79 CreatePixmap
80 CreateGC
79 FreeGC
154 PutImage
23210 AllocColor
2 QueryExtension
So, we see that a LOT of colors are being allocated quickly, and a lot of
images are being put up to the X server in PutImage.
Unfortunately, I am unable to catch it in the act (with the debugger or Xmon),
so I cant tell you exactly where the problem is :(
Keep in mind, this is the Application crashing, not the X server.
Any ideas?
Brian
--- Alan Hourihane <alanh@fairlite.demon.co.uk> wrote:
> On Mon, Nov 05, 2001 at 09:16:24AM -0800, Brian Genisio wrote:
> > Hey all,
> >
> > I have 2 internal application which uses mostly XPutImage calls for one,
> and
> > XpmCreatePixmapFromXpmImage calls for the other.
> >
> > Both of these have gotten the following error randomly. I havn't a clue
> why.
> > Any ideas???
> >
> > XIO: fatal IO error 105 (No buffer space available; the socket cannot be
> > connected) on X server "<MYHOST>:0.0"
> > after 263 requests (262 known processed) with 0 events remaining.
> >
> I'd run up gdb or similar and single step your application to find out
> where these errors are being caused.
>
> Basically error 105 is ENOBUFS, which as it states is 'No buffer space
> available'. This it seems is something that Cygwin is throwing back from
> the kernel to the Xserver.
>
> Are you running the latest cygwin ? 1.3.3 ?
>
> Alan.
__________________________________________________
Do You Yahoo!?
Find a job, post your resume.
http://careers.yahoo.com