For more information on memory debugging with WDB, see the Debugging Dynamic Memory Usage Errors Using HP WDB whitepaper at the HP WDB Documentation webpage at: http://www.hp.com/go/wdb.
14.10.1 When to suspect a memory leakYou should suspect a memory leak in the code when you notice that the system is running out of swap space or running slower, or both.
Applications or
If the system is running out of swap space, programs will fail with
Programs with these attributes are not supported:
•CMA or DCE threaded programs on 11.x
•Memory checking features. These features work only in programs that directly or indirectly call malloc, realloc, free, mmap, or munmap from the standard C library libc.sl.
•Programs that link the archive version of the standard C library, libc.a, or the core library, libcl.a, on
NOTE: Linker with version number B.11.19 or higher is required for debugging memory problems.
•From HP WDB 5.7 onwards, the archive version of the run time check library, librtc.a, is not available. You must use the shared version of the library, librtc.[slso], instead.
14.10.3Memory Debugging MethodologiesWDB enables you to debug memory problems in applications written for
WDB provides several commands that help expose
158