Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!ames!sun-barr!decwrl!chico.pa.dec.com!klee
From: klee@chico.pa.dec.com (Ken Lee)
Newsgroups: comp.windows.x
Subject: Re: SIGPIPE in HP 9000 (319,350)
Keywords: SIGPIPE HP
Message-ID: <1952@bacchus.dec.com>
Date: 20 Oct 89 16:43:52 GMT
References: <300@goya.dit.upm.es>
Sender: news@decwrl.dec.com
Reply-To: klee@decwrl.dec.com
Organization: DEC Western Software Laboratory
Lines: 23

In article <300@goya.dit.upm.es>, elicegui@ts.tid.es (elicegui) writes:
> I am working using an HP 9000/(319,350) workstation running 6.5 HP-UX.
> I am working with HP widgets set.
> 
> I have a problem in a aplication when I create many widgets. The
> client process generates the signal SIGPIPE /* write on a pipe with
> no one to read it */
> If I give more priority to the client process, the prohgram finishes
> well.

Sounds like a bug in your server.  The server probably generates lots
of Expose or other events for all your widgets.  The client reads them
much more slowly than the server generates them, so the server queue
fills up.  The server then mistakenly thinks the client is dead and
drops the connection, giving the client a SIGPIPE.  You should try
getting your server to do something more useful in this case, like
allocating another buffer.  Alternatively, you can use Motif gadgets
which may cause fewer events to be generated.

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