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

Yes. WDB supports detection of leaks in a third party code also.
4 What are the commands that the batch mode of memory-debugging does not support?
For more information on the commands that are supported in batch mode, see
“Summary of Memory Debugging Commands” (page 75)
5 Can WDB debug applications with user-defined memory management routines?
WDB can debug applications with memory management routines that are either user
defined or are wrappers to the default memory management routines.
NOTE:
• This feature is not supported in the batch and the attach modes of debugging.
• In interactive mode, this feature will result in calls to the user defined memory
management routines being re-routed to default memory management routines.
6 Which version of WDB supports debugging of applications with custom allocators?
WDB 5.5 and above versions support the debugging of applications with custom
allocators.
7 Does WDB report the exact instant when the block becomes a leak?
No. WDB does not provide information on when the leak occurred. It reports only
the allocation stack trace of the leaked block and does not report the stack trace
where the block leaked.
8 Does WDB support debugging of C++ applications with calls to new() and
delete()?
Yes. WDB supports debugging of C++ applications with new() and delete()
calls only if they internally call malloc() and free().
9 Does WDB support memory-debugging of long running applications?
Yes. WDB supports debugging of long running applications such as daemons.
However, the daemons must be started with an explicit LD_PRELOAD of the correct
version (32-bit or 64-bit) of librtc.[sl|so], so that WDB can debug memory
when it later attaches to the daemon process.
10 What is the work-around when the following message is displayed, when attempting
to view the leak report with the info leaks command?
(gdb) info leaks
Current thread is blocked. Cannot detect leaks now.
You can switch execution to a thread, which is not blocked. To switch execution to
a different thread, enter the following command at the gdb prompt:
(gdb)thread <thread-id>
11 Does the debugger find leaks in the executable from the startup of the application
when debugging the application in attach mode?
106