X-Git-Url: http://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_memleaks.3x.html;h=19ed239ea5cc43c5fd9037ab9ab43992ada69db5;hp=1d0578a2e533df67a519b3b264ca275715603b3e;hb=ed646e3f683083e787c6ba773364401dc9fa9d40;hpb=71c0306f0824ef2b10c4c5813fb003db48f3012e diff --git a/doc/html/man/curs_memleaks.3x.html b/doc/html/man/curs_memleaks.3x.html index 1d0578a2..19ed239e 100644 --- a/doc/html/man/curs_memleaks.3x.html +++ b/doc/html/man/curs_memleaks.3x.html @@ -1,7 +1,6 @@ - + + + curs_memleaks 3x -

curs_memleaks 3x

-
+

curs_memleaks 3x

-
-curs_memleaks(3x)                                     curs_memleaks(3x)
+curs_memleaks(3x)                                            curs_memleaks(3x)
 
 
 
 
-
-

NAME

-       _nc_freeall _nc_free_and_exit - curses memory-leak
-       checking
+

NAME

+       _nc_freeall _nc_free_and_exit - curses memory-leak checking
 
 
-
-

SYNOPSIS

+

SYNOPSIS

        #include <curses.h>
 
        void _nc_freeall(void);
        void _nc_free_and_exit(int);
 
 
-
-

DESCRIPTION

-       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
-       build  time  using  the --disable-leaks option.  That com-
-       piles-in code that frees memory that normally would not be
+

DESCRIPTION

+       These  functions  are  used to simplify analysis of memory leaks in the
+       ncurses library.  They are normally not available; they must be config-
+       ured  into  the library at build time using the --disable-leaks option.
+       That compiles-in code that frees memory  that  normally  would  not  be
        freed.
 
-       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.
+       Any implementation of curses must not free the memory associated with a
+       screen, since (even after calling endwin), it must be available for use
+       in  the next call to refresh(3x).  There are also chunks of memory held
+       for performance reasons.  That makes it hard to analyze curses applica-
+       tions 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
-       code to pass to the exit routine.
+       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.
 
 
-
-

RETURN VALUE

+

RETURN VALUE

        These functions do not return a value.
 
 
-
-

PORTABILITY

+

PORTABILITY

        These functions are not part of the XSI interface.
 
 
-
-

SEE ALSO

+

SEE ALSO

        curses(3x).
 
 
 
-                                                      curs_memleaks(3x)
+                                                             curs_memleaks(3x)
-
-
-Man(1) output converted with -man2html -
+
+ +