Re: tparm allocated strings should be freed ater use?

[Thomas Dickey]

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
> complaining.
>
> 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.
>
> Regards,
>
>
>
>
>      ___________________________________________________________
> Yahoo! Answers - Got a question? Someone out there knows the answer. Try it
> now.
> http://uk.answers.yahoo.com/
>
>
> _______________________________________________
> Bug-ncurses mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-ncurses

--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net