Path: utzoo!attcan!uunet!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: A solution for Server crashes for X11R4 on Sun386
Message-ID: <9003201355.AA01970@expire.lcs.mit.edu>
Date: 20 Mar 90 13:55:46 GMT
References: <5607@omepd.UUCP>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 7

Your "facts" in no way substantiate your claim.  Based on your evidence,
it's just as likely there's an uninitialized variable somewhere that's
causing the problem, and it just happens to get tickled by the particular
stack/whatever environment under the 386/cc combination.  Compiling with -g
or with a different compiler can change that environment.  Without more
proof, I'd say the server code is just as suspect as the compiler.  As
usual, a stack trace of the crash is often necessary for diagnosis.