contig_free(9r) [osf1 man page]

contig_free(9r) 														   contig_free(9r)

NAME

       contig_free - General: Frees a block of memory previously allocated by contig_malloc

SYNOPSIS

       #include <sys/malloc.h>

       void contig_free(
	       void *addr,
	       u_long size,
	       int type );

ARGUMENTS

       Specifies  the  address	of  the memory being freed. This address was returned in a previous call to contig_malloc.  Specifies the size (in
       bytes) of the memory being freed. You should pass the same value used to allocate this memory in the call to contig_malloc.  Specifies  the
       purpose	for  which  the  memory is being allocated (or freed). The memory type constants are defined in the file /usr/sys/include/sys/mal-
       loc.h. Examples of memory type constants are M_DEVBUF (device driver memory), M_KTABLE (kernel table memory), M_RTABLE (routing tables mem-
       ory), and so forth.

DESCRIPTION

       The contig_free routine frees the memory allocated in a previous call to contig_malloc. If the memory came from the saved memory pool, con-
       tig_free puts it back in the saved memory pool; otherwise, the interface frees the memory to the virtual memory subsystem.

RETURN VALUES

       None

SEE ALSO

       Routines: contig_malloc(9r)

																   contig_free(9r)

curs_memleaks(3X)														 curs_memleaks(3X)

NAME

       _nc_freeall _nc_free_and_exit - curses memory-leak checking

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 con-
       figured 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 associated 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 reasons.	That makes it hard to analyze  curses  ap-
       plications  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.

RETURN VALUE

       These functions do not return a value.

PORTABILITY

       These functions are not part of the XSI interface.

SEE ALSO

       curses(3X).

																 curs_memleaks(3X)