XL Fortran Enterprise Edition for AIX : User's Guide - IBM

C Function prototype Fortran usage example Description
void _dump_allocated_delta
(int size);
integer(4) :: size=4
call _dump_allocated_delta &
(%val(size))
This routine prints information to
stderr about each memory block
that is currently allocated or was
allocated using the debug memory
management routines since the last
call to _dump_allocated or
_dump_allocated_delta. size indicates
how many bytes of each memory
block are to be printed, as follows:
Negative size
All bytes are
displayed.
0 size No bytes are
displayed.
Positive size
Specified number
of bytes are
displayed.
void heap_check(void); call _heap_check() This routine does consistency
checking for memory blocks that
have been allocated using the
debug memory-management
routines. It checks that your
program has not overwritten freed
storage or memory outside the
bounds of allocated blocks.
All of the debug
memory-allocation routines (debug
version of malloc, and so on)
invoke heap_check automatically. It
may also be invoked explicitly in
areas of code where a user believes
there may be memory problems.
Calling heap_check frequently can
increase the memory requirements
and affect the performance of a
program. The HD_SKIP
environment variable may be used
to control how often the debug
memory procedures check the
heap.
Note that the errors are detected
when the heap_check routine is
invoked, not at the point of error
in the program.
Environment Variables
The debug libraries support the following environment variables:
HD_SKIP=increment [,start]
Control how often heap_check is invoked from the
debug versions of the memory-management
routines. increment indicates how often you want
the debug functions to check the heap. start
specifies that the skipping of heap checks should
begin after the debug memory routines have been
Problem Determination and Debugging 385