X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_memleaks.3x.html;h=499374aabe590fa955b397afe5343bd941c08c29;hp=7d89feab6b5fe9bf3f53f446f3672305443cea2b;hb=58552e8c761a70f8f0bd591fecdf576fa8216e3e;hpb=c6cfd97b8beaf0f6deafbf8aac7281cf6aa7f012 diff --git a/doc/html/man/curs_memleaks.3x.html b/doc/html/man/curs_memleaks.3x.html index 7d89feab..499374aa 100644 --- a/doc/html/man/curs_memleaks.3x.html +++ b/doc/html/man/curs_memleaks.3x.html @@ -1,6 +1,6 @@ @@ -38,30 +38,26 @@
-curs_memleaks(3x) curs_memleaks(3x) --
+
_nc_freeall _nc_free_and_exit - curses memory-leak checking --
+
#include <curses.h> void _nc_freeall(void); void _nc_free_and_exit(int); --
+
These functions are used to simplify analysis of memory leaks in the ncurses library. They are normally not available; they must be configured into the library at @@ -71,32 +67,30 @@ Any implementation of curses must not free the memory as- sociated with a screen, since (even after calling endwin), - it must be available for use in the next call to refresh. - There are also chunks of memory held for performance rea- - sons. That makes it hard to analyze curses applications - for memory leaks. To work around this, one can build a - debugging version of the ncurses library which frees those - chunks which it can, and provides these functions to free - all of the memory allocated by the ncurses library. - - The _nc_free_and_exit function is the preferred one since - some of the memory which is freed may be required for the - application to continue running. Its parameter is the + it must be available for use in the next call to re- + fresh(3x). There are also chunks of memory held for per- + formance reasons. That makes it hard to analyze curses + applications for memory leaks. To work around this, one + can build a debugging version of the ncurses library which + frees those chunks which it can, and provides these func- + tions to free all of the memory allocated by the ncurses + library. + + The _nc_free_and_exit function is the preferred one since + some of the memory which is freed may be required for the + application to continue running. Its parameter is the code to pass to the exit routine. --
+
These functions do not return a value. --
+
These functions are not part of the XSI interface. --
+
curses(3x).