Path: utzoo!attcan!uunet!ginosko!husc6!bloom-beacon!EXPO.LCS.MIT.EDU!rws From: rws@EXPO.LCS.MIT.EDU Newsgroups: comp.windows.x Subject: Re: Signals and X Message-ID: <8908132123.AA00567@expire.lcs.mit.edu> Date: 13 Aug 89 21:23:35 GMT References: <8908121821.AA17340@expo.lcs.mit.edu> Sender: daemon@bloom-beacon.MIT.EDU Organization: The Internet Lines: 7 You don't give any clue to where the program is crashing (when will people ever learn to provide this kind of information?), so it's rather difficult to give an explanation. But, if you're trying to use the MIT Xlib implementation in an environment with System V signal semantics (particularly as they apply to the write system call), you're in for real problems. System V signals are awful to deal with, and we don't claim that R3 works in that environment. If that isn't your problem, then you'll have to provide more information.