Debugging Dynamic Memory Usage Errors Using HP WDB (766161-001, March 2014)

[/opt/langtools/lib/hpux32/librtc.sl]
(3) 0x60000000cac17200 __rtc_free + 0x160 at
../../../Src/gnu/gdb/infrtc.c:2977
[/opt/langtools/lib/hpux32/librtc.sl]
(4) 0x0000000004000bc0 main + 0x230 at memtest.c:25[memtest]
(5) 0x60000000c0029000 main_opd_entry + 0x50[/usr/lib/hpux32/dld.so]
$ cat .//memtest.8494.leaks
40 bytes leaked in 10 blocks
No. Total bytes Blocks Address Function
0 40 10 0x4006e7d0 main()
------------------------------------------------------------
Detailed Report
------------------------------------------------------------
40 bytes leaked in 10 blocks (100.00% of all bytes leaked)
These range in size from 4 to 4 bytes and are allocated
#0 main() at memtest.c:19
#1 main_opd_entry() from /usr/lib/hpux32/dld.so
------------------------------------------------------------
$ cat memtest.8494.heap
40 bytes allocated in 10 blocks
No. Total bytes Blocks Address Function
0 40 10 0x4006e8f0 main()
------------------------------------------------------------
Detailed Report
------------------------------------------------------------
40 bytes in 10 blocks (100.00% of all bytes allocated)
These range in size from 4 to 4 bytes and are allocated
#0 main() at memtest.c:19
#1 main_opd_entry() from /usr/lib/hpux32/dld.so
------------------------------------------------------------
Nudge/Signal Triggered Batch Mode Reporting
Batch mode of RTC (heap, leak and corruption) reports generation is explained in previous few
sections. HP WDB 6.3 and prior versions mandated the process, running under batch mode, to
exit gracefully to be able to generate those reports.
With the advent of HP WDB 6.4, you can now obtain RTC reports at any point in time during
execution of the process (running under batch mode) and that too almost effortlessly. A signal is
used as a nudge to trigger report generation.
You initially need to specify the signal, you wish to use as nudge, in the rtcconfig file. Start the
process in batch mode. During execution when you wish to generate the RTC reports just send the
specified signal to that process. After report generation, the process will resume normal execution.
In a single program run, you can obtain reports any number of times. Each report thus obtained
Supported Modes of Memory-debugging in WDB 57