Path: utzoo!mnetor!uunet!husc6!think!ames!oliveb!pyramid!hplabs!hp-pcd!hpcvlx!lori
From: lori@hpcvlx.HP.COM (Lori Cook)
Newsgroups: comp.windows.x
Subject: Re: malloc/free bug in server?
Message-ID: <1610008@hpcvlx.HP.COM>
Date: 22 Mar 88 16:11:08 GMT
References: <gWEi1Yy00hk=M4tlw2@cs.cmu.edu>
Organization: Hewlett-Packard Co., Corvallis, OR, USA
Lines: 15


	I have 'run' into a similar problem. If your message is correct about
freeing non-malloc'ed memory, then I suggest you start looking closely at all
calls to 'free' and 'XFree'. I know that in R1 version of the X11 code, the
'XFree' routine had a bug. If you passed a NULL pointer to 'XFree' it would
core dump on our machines. The same is true (appears true) with 'free'. While
in R2, the bug has been fixed in 'XFree' so that it does nothing if passed a
null pointer, the safest bet is to check the pointer that is to be passed to
either of these routine, and only calling the routine if the pointer is
non-NULL.
	Hope this helps!


						Regards
						Lori A. Cook