2.Run the program.
3.Start a debugging session as follows:
gdb
4.Use info heap and info leaks commands to obtain a memory analysis report of the application.
NOTE: 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.7 Configuring memory debugging settingsThe following configuration settings are supported to control the level of details of information required to be displayed when debugging memory leaks.
14.10.7.1 Specifying the stack depth
Memory debugging reduces the performance of an application by
The set
To set the depth of the stack frames that is collected by WDB, enter the following command at the gdb prompt:
$ set
The stack depth, [num], is the number of stack frames that WDB collects for each allocation.
You can specify a higher value for [num] to view more stack frames for each reported allocation. However, the performance of the application is reduced because of the increased stack depth.
14.10.7.2 Specifying minimum leak size
WDB enables you to specify the minimum leak size for stack trace collection to improve the program's performance.
Stack trace collection slows down the program because it occurs on every allocation call. Therefore, if the program is
You can improve performance by using the command:
14.10 Debugging Memory Problems 173