Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!julius.cs.uiuc.edu!apple!olivea!orc!inews!pinkas From: pinkas@st860.intel.com (Israel Pinkas) Newsgroups: comp.windows.x Subject: Re: XFreeColors bug Message-ID: Date: 4 Dec 90 19:04:44 GMT References: <1990Nov30.205231.21765@Solbourne.COM> Sender: news@inews.intel.com Organization: Software Technologies, INTeL Corporation, Santa Clara, CA Lines: 33 In-reply-to: garya@garya.Solbourne.COM's message of 30 Nov 90 20:52:31 GMT In article <1990Nov30.205231.21765@Solbourne.COM> garya@garya.Solbourne.COM (Gary Aitken) writes: > The following program demonstrates an XFreeColors Bug in the X11R4 library. > If one creates a private colormap and allocates cells in it via the create > call, those cells cannot be freed. > However, if the cells are not allocated during the create, but are instead > specifically allocated later, they can be freed. > ================================ cut here =================== > /* > * If: > * A colormap is created and all cells are allocated in the create call > * Then: > * An attempt to free one of the allocated cells will fail. > */ [Code deleted] Funny, that's what my documentation say it will do. The man page states: However, in all cases, none of these entries can be freed by using XFreeColors. -Israel Pinkas Intel Corp -- -------------------------------------- Disclaimer: The above are my personal opinions, and in no way represent the opinions of Intel Corporation. In no way should the above be taken to be a statement of Intel. UUCP: {amdcad,decwrl,hplabs,oliveb,pur-ee,qantel}!intelca!mipos3!st860!pinkas ARPA: pinkas%st860.intel.com@relay.cs.net CSNET: pinkas@st860.intel.com