Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!island!cat
From: cat@island.uu.net (Cathleen Greenberg)
Newsgroups: comp.windows.x
Subject: Re: XIOErrorHandler
Message-ID: <1130@island.uu.net>
Date: 13 Oct 89 17:16:36 GMT
References: <100689.093908.dan@watson.ibm.com>
Reply-To: cat@island.uu.net (Cathleen Greenberg)
Organization: Island Graphics, Marin County, California
Lines: 29

In article <100689.093908.dan@watson.ibm.com> dan@watson.ibm.COM (Walt Daniels) writes:
>Submitting for a friend (Walt)
>Is this an IBM problem, or is it a genetic defect?
>------------
> I really think that Xlib should do something with
>SIGPIPE signals other than letting the default action take place.
>This would allow the XIOErrorHandler (Xlib's default, or user
>specified) to get invoked.


To answer the question -- no it is not just IBM -- I have the same problem
on a sun 3/60 -- and I agree that Xlib should do something other than
hand over control so that the only message is broken pipe.


On a similar note -- does anyone else have problems with large Ximages??
When reading (and sometimes writing) TIFF files, I will either get
an XIO error (broken pipe) or sometimes the program quits with
no message at all.  The program handles images better on an NCD X terminal
than on a sun 3/60 -- anyone have any ideas?? Anyone else experiencing this
phenomenon??

--Cathleen Greenberg
  ...sun!island!cat
-- 
--------------------------------------------------------------------------------
Cathleen Greenberg				work: (415) 491-1000
  						sun!island!cat
  						ucbcad!island!cat