Thomas,
(thank you for maintaining ncurses for so long.)
But doing that, some features of ncurses (like any curses implementation)
would not work. In short the _nc_freeall, etc., are only useful for
debugging, not for a production library.
But this precisely is the point i do not
Hi,
i stumbled over this bug, too, and write to ask what the state of resolution is.
The libncurses5-dbg is not distributed with --disable-leaks, at time of writing.
If no semantic issues are know i would suggest not only to build the debugging
library with --disable-leaks, but the production
On Fri, 8 May 2009, Lars Doelle wrote:
Hi,
i stumbled over this bug, too, and write to ask what the state of resolution is.
The libncurses5-dbg is not distributed with --disable-leaks, at time of writing.
--disable-leaks won't (by itself) free all leaks.
For that, you'd need the non-public
Package: libncurses5
Version: 5.6+20080713-1
Severity: normal
According to valgrind, libncurses5 allocates approximately 118k that is
never freed:
==31792== 8 bytes in 1 blocks are still reachable in loss record 1 of 23
==31792==at 0x4C200FC: calloc (vg_replace_malloc.c:397)
==31792==by
On Sat, 2 Aug 2008, brian m. carlson wrote:
Package: libncurses5
Version: 5.6+20080713-1
Severity: normal
According to valgrind, libncurses5 allocates approximately 118k that is
never freed:
read the INSTALLATION file in sources, which describes the --disable-leaks
option
--
Thomas E.
On Sat, 2 Aug 2008, brian m. carlson wrote:
Package: libncurses5
Version: 5.6+20080713-1
Severity: normal
According to valgrind, libncurses5 allocates approximately 118k that is
never freed:
from INSTALL:
--disable-leaks
For testing, compile-in code that frees memory that
On Sat, Aug 02, 2008 at 07:46:49PM -0400, Thomas Dickey wrote:
On Sat, 2 Aug 2008, brian m. carlson wrote:
Package: libncurses5
Version: 5.6+20080713-1
Severity: normal
According to valgrind, libncurses5 allocates approximately 118k that is
never freed:
from INSTALL:
--disable-leaks
On Sun, 3 Aug 2008, brian m. carlson wrote:
I personally don't believe refresh is required to work after a
delwin(stdscr), since
Calling delwin deletes the named window, freeing all memory associated
with it
except that it doesn't free all the memory associated with it. It does
free
8 matches
Mail list logo
