[comp.windows.x] XIO error from server??

ekberg@ti-csl.csc.ti.COM (07/12/90)

While running an internally written InterViews Unidraw client on the MIT X11R4
sample server for a color Sun4/110 using SunOS 4.0 the following message was
generated:

	XIO: fatal IO error 9
	     (Bad file number) on X server "unix:0.0"
	after 2848 requests (2846 known processed)
	with 0 events remaining

I searched through the ddx/sun/ directory and didn't find anything that
matched.  Does anyone have any ideas what would generate this kind of error?

(Yes, I know I'm being very vague, but hopefully this is enough information.)

  -- tom (aisle C-4Q), ekberg@csc.ti.com

klee@wsl.dec.com (Ken Lee) (07/12/90)

In article <9007112049.AA12579@osage.csc.ti.com>, ekberg@ti-csl.csc.ti.COM
writes:

|> 	XIO: fatal IO error 9

Xlib will generate errors like this when it encounters fatal system
call errors.  The error 9 refers to the UNIX system error number, in
this case EBADF, a bad file descriptor.  For some reason one of the
descriptors Xlib has been reading or writing has gone bad.  I've never
seen this before.

Ken Lee
DEC Western Software Laboratory, Palo Alto, Calif.
Internet: klee@wsl.dec.com
uucp: uunet!decwrl!klee