From: Matan Ziv-Av (matan@svgalib.org)
Date: Wed 11 Oct 2000 - 18:15:00 IST
On Wed, 11 Oct 2000, Robin wrote: > I found out that the leaking allocations where caused by 1 > particular function. The card/driver specific ..._modeavailable( > function (eg sis_modeavailable()). > For some drivers the functions where ok, some weren't. (including > skeleton.c) > > 107: modeinfo = > __svgalib_createModeInfoStructureForSvgalibMode(mode); > > > 112: modeinfo = > __svgalib_createModeInfoStructureForSvgalibMode(mode); > > > The allocation caused in line 107 is never freed, and actually > never used. Removing this lines solves the problem. > > Is this fixed in the current release ? Thanks for this analysis. The problem is not fixed, but will be in the next pre-release. -- Matan Ziv-Av. matan@svgalib.org ------------------------------------------------------------------ Unsubscribe: To: listbot@svgalib.org Body: unsubscribe linux-svgalib
This archive was generated by hypermail 2.1.4 : Wed 21 Jan 2004 - 22:10:23 IST