X-Git-Url: http://ncurses.scripts.mit.edu/?a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_memleaks.3x.html;h=19ed239ea5cc43c5fd9037ab9ab43992ada69db5;hb=ed646e3f683083e787c6ba773364401dc9fa9d40;hp=499374aabe590fa955b397afe5343bd941c08c29;hpb=8e397cccba0aad135cb9a8a353756f4273a7cdf6;p=ncurses.git diff --git a/doc/html/man/curs_memleaks.3x.html b/doc/html/man/curs_memleaks.3x.html index 499374aa..19ed239e 100644 --- a/doc/html/man/curs_memleaks.3x.html +++ b/doc/html/man/curs_memleaks.3x.html @@ -40,14 +40,13 @@

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
+       _nc_freeall _nc_free_and_exit - curses memory-leak checking

SYNOPSIS

@@ -58,28 +57,24 @@

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
+       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 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.
+       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

@@ -95,7 +90,7 @@
 
 
 
-                                                      curs_memleaks(3x)
+                                                             curs_memleaks(3x)