Debugging Dynamic Memory Usage Errors Using HP WDB (5900-1474; WDB 6.2; January 2011)

Table 16 Commonly Used Commands for Memory Debugging (continued)
Batch ModeInteractive Mode/Attach ModeDescription
Not supported in Batch Modeset heap-check interval
<num>
Starts the incremental heap growth
profile. All allocations prior to the
execution of this command are
ignored. If incremental heap
growth profile is already on,
executing this command resets the
counters and starts a fresh
collection. The interval is specified
in seconds.
Not supported in Batch Modeset heap-check repeat
<num>
Enables you to specify the number
of intervals for which WDB must
collect the incremental heap
growth. The default value is 100.
Every repeat of the interval tracks
heap allocation during that
interval.
Not supported in Batch Modeinfo heap intervalCreates a detailed report of the
heap growth. The data for each
interval has the start and end time
of the interval.
Not supported in Batch Modeset heap-check
high-mem-count <X_number>
Stops when break value has
moved <X_number> times
Not supported in Batch Modeinfo heap high-memDisplays the number of times
break value changes for a given
run
Not supported in Batch Modeinfo heap
<process|arenas>
Displays the high level
memory-usage of a process or an
arena. Lists the number of free
blocks, used blocks, small blocks,
holding blocks, node blocks and
regular blocks.
Not supported in Batch Modeset heap-check
header-size <no of bytes>
Sets the Header guard for each
block of the allocated memory.
The default number of bytes for
the header is 16 bytes if this
option is not used.
Not supported in Batch Modeset heap-check
footer-size <no of bytes>
Sets the Footer guard for each
block of the allocated memory.
The default number of bytes for
the footer is one byte if this option
is not used.
Not supported in Batch Modeset heap-check
retain-freed-blocks
<on/off>
Enables you to detect the dangling
pointers and in block corruption
of freed blocks.
Summary of Memory Debugging Commands 77