Path: utzoo!attcan!uunet!decwrl!bacchus.pa.dec.com!wsl.dec.com!klee
From: klee@wsl.dec.com (Ken Lee)
Newsgroups: comp.windows.x
Subject: Re: Signals and X--a problem
Message-ID: <1990Aug1.162845.23054@wrl.dec.com>
Date: 1 Aug 90 16:28:45 GMT
References: <1028@meaddata.mead.UUCP>
Sender: news@wrl.dec.com (News)
Reply-To: klee@wsl.dec.com
Organization: DEC Western Software Laboratory
Lines: 23


In article <1028@meaddata.mead.UUCP>, marko@mead.UUCP (Mark Osbourne) writes:
|> The problem we're having seems to be that the Xlib functions to create
|> the request for the server are being interrupted by another signal.
|> The errors we end up getting are mostly bad request, but others like
|> bad drawable occasionally show up.

A few things you might try:

1.  Xlib has LockDisplay macros around critical sections of code.  You
could try defining these to block signals.

2.  Don't do Xlib things in your signal handlers.  Instead, set a flag
and do you X stuff afterwards.

3.  Open 2 server connections.  Do your normal X stuff on 1 connection
and your signal handler stuff on the other.  This assumes, of course,
that you can prevent signals handlers from interrupting each other.

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