X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_memleaks.3x.html;h=74b910d110de3c391dd01124fe80e41ee2ed3fce;hp=b36442c4be62a915edb3a9d0f37957778d56d923;hb=d97989d1e0db7282c723cabb44b991b951790006;hpb=027d0c57c4c4d6690e8d8727888d3282dbe9aa86 diff --git a/doc/html/man/curs_memleaks.3x.html b/doc/html/man/curs_memleaks.3x.html index b36442c4..74b910d1 100644 --- a/doc/html/man/curs_memleaks.3x.html +++ b/doc/html/man/curs_memleaks.3x.html @@ -1,6 +1,6 @@ - + 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
+

NAME

+       _nc_freeall, _nc_free_and_exit, _nc_free_tinfo - curses memory-leak
        checking
 
 
-
-

SYNOPSIS

+

SYNOPSIS

        #include <curses.h>
 
        void _nc_freeall(void);
        void _nc_free_and_exit(int);
+       void _nc_free_tinfo(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.  When using the specially configured  debugging
+       version  of  the ncurses library, applications can call functions which
+       free those chunks of memory, simplifying  the  process  of  memory-leak
+       checking.
 
-       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 are named with a "_nc_" prefix because they are not in-
+       tended for use in the non-debugging library:
 
+       _nc_freeall
+            This frees (almost) all of the memory allocated by ncurses.
 
-
-

RETURN VALUE

+       _nc_free_and_exit
+            This frees the memory allocated by ncurses (like _nc_freeall), and
+            exits the program.  It is preferred over _nc_freeall since some of
+            that memory may be required to keep the application running.  Sim-
+            ply exiting (with the given exit-code) is safer.
+
+       _nc_free_tinfo
+            Use  this  function  if only the low-level terminfo functions (and
+            corresponding library) are used.  Like _nc_free_and_exit, it exits
+            the program after freeing memory.
+
+
+

RETURN VALUE

        These functions do not return a value.
 
 
-
-

PORTABILITY

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

PORTABILITY

+       These functions are not part of X/Open Curses; nor do other implementa-
+       tions of curses provide a similar feature.
 
 
-
-

SEE ALSO

+

SEE ALSO

        curses(3x).
 
 
 
-                                                      curs_memleaks(3x)
+                                                             curs_memleaks(3x)