Re: Could --disable-leaks be made a runtime switch?

[Steve Litt]

On Tuesday 12 February 2008 11:01, Thomas Dickey wrote:
> On Tue, 12 Feb 2008, Avery Pennarun wrote:
> > On 11/02/2008, Steve Litt <address@hidden> wrote:
> >> nCurses can be made to work right with Valgrind during compile
> >> by ./configure --disable-leaks. Trouble is, I have to have two different
> >> nCurseses.
> >>
> >> Would it be difficult to have make the --disable-leaks decision at
> >> runtime rather than at compile time? That way I could use just one
> >> nCurses -- presumably the one that my distro uses to make all their
> >> tools.
> >
> > Isn't there a function you can call at the end of your program that
> > does the same thing as --disable-leaks?  I seem to remember using such
> > a thing in the past.
>
> There are a few functions that can be called to free up the "permanent"
> memory, but that's part of the --disable-leaks feature.

Thanks Thomas,

If you can tell me all the functions necessary to call at the end of the 
program to free all memory allocated by ncurses, that's good enough for me. I 
can simply call all those functions, in my program, using my current nCurses 
software, and presumably Valgrind won't find memory leaks in nCurses.

I know _nc_free_and_exit() is one of those functions. What are the others, and 
in what order should they be called?

Thanks

StevET

-- 
Steve Litt
Author: Universal Troubleshooting Process books and courseware
http://www.troubleshooters.com/

(Legal Disclaimer) Follow these suggestions at your own risk.