Path: utzoo!attcan!uunet!husc6!bloom-beacon!VAX.BBN.COM!ado From: ado@VAX.BBN.COM (Buz Owen) Newsgroups: comp.windows.x Subject: Re: MALLOC_0_RETURNS_NULL Message-ID: <8806211450.AA01652@ATHENA.MIT.EDU> Date: 21 Jun 88 03:08:53 GMT References: <19880617120851.3.RWS@KILLINGTON.LCS.MIT.EDU> Sender: daemon@bloom-beacon.MIT.EDU Organization: The Internet Lines: 8 Maybe this idea will be of some value to someone... MALLOC_0_RETURNS_NULL sounds like a compile time option that could probably be checked at startup time, by calling malloc(0) and looking at the result, assuming it did not bomb. There are probably are other configuration options that could be similarly checked. A suite of such checks could be written, probably pretty easily, and included in some program run by make when the system is compiled, and/or in the startup of some appropriate program, maybe the x server. Any false assumption would produce a helpful message about the incorrect option.