[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: tparm allocated strings should be freed ater use?

From: Thomas Dickey
Subject: Re: tparm allocated strings should be freed ater use?
Date: Mon, 13 Aug 2007 09:37:14 -0400 (EDT)

On Mon, 13 Aug 2007, chinlu chinawa wrote:

Hello Thomas, and everyone

valgrind is reporting me memory leaks caused by tparm,
so I wanted to ask the right way of using it.

To check leaks, you have to keep in mind that some buffers are allocated
"permanently", and use the --disable-leaks configure option to modify the
library to turn on extra features that let you audit memory leaks.

Some of the memory can only be freed using _nc_free_and_exit(), as is done in tic, infocmp, etc., as well as the test programs.

By reading it's man page I think I should free strings
returned by it, though even doing it after a call to
tputs doesn't seem to keep valgrind away from

I know I can generate suppresion-rules so as to make
it shut, the point is if I'd be right of doing so, or
whether I'm doing something wrong.


Yahoo! Answers - Got a question? Someone out there knows the answer. Try it

Bug-ncurses mailing list

Thomas E. Dickey

reply via email to

[Prev in Thread] Current Thread [Next in Thread]