The debugger assigns each leak a numeric identifier.

7.To display a stack trace for a specific leak, use the info leak command and specify the number from the list associated with a leak:

(gdb) info leak 2

245 bytes leaked in 8 blocks (10.05% of all bytes leaked) These range in size from 26 to 36 bytes and are allocated in strdup ()

in link_the_list () at test.c:55 in main () at test.c:13

in _start ()

14.10.5Debugging Memory in Batch Mode

HP WDB supports batch mode memory leak detection, also called batch Run Time Checking (Batch RTC). Most of the memory debugging features supported in interactive mode are also supported in batch mode.

NOTE: The batch mode commands may not always work when invoked through a shell script.

14.10.5.1 Setting Configuration Options for Batch Mode

You can specify the batch mode configuration through a configuration file called rtcconfig. The configuration file supports these variables:

check_free=onoff (or) set heap-check free <on/off>

check_heapheap=onoff (or) set heap-check <on/off>

check_leaksleaks=onoff (or) set heap-check leaks <on/off>

check_string=onoff (or) set heap-check string <on/off>

check_boundsbounds=onoff (or) set heap-check bounds <on/off>

files=<file1:file2:...fileN>

Enables detection of multiple incorrect free of memory

Enables heap profiling.

Enables leak detection.

Enables detection for writing out of boundary for strcpy, strncpy, memcpy, memccpy, memset, memmove, bzero, bcopy.

Enables checking of bounds corruption.

Specifies the executables for which memory leak detection is enabled. If files option is not specified, after setting BATCH_RTC=on, RTC will instrument ALL executables.

164 HP-UX Configuration-Specific Information