HP WDB 5.9 Release Notes

NOTE: +mem_check to chatr command can be used to automatically preload the

library for memory debugging. The +mem_check option to chatr command doesn’t

support automatic preloading of libraries needed for thread debugging.

Availability of a new compiler runtime check option +check=thread

The new compiler runtime check option +check=thread enables batch mode thread

debugging features of HP WDB, without setting any other environment at runtime.

+check=thread must only be used with multi-threaded programs. It is not enabled

by +check=all. This feature is available only for compiler versions A.06.20 and later.

Using Batch RTC to Process the .gdbinit File

Batch RTC now enables processing of the .gdbinit file. You can use the .gdbinit

file to specify path settings such as dir, objectdir, and pathmap to set the path of

the source and object files in case the source or object paths are different than the current

directory, so that the generated RTC reports display the symbol names and line numbers

correctly. This feature is optionally enabled only when the RTC_PROCESS_GDBINIT

variable is set to 1. This feature has some limitations on what commands in the

.gdbinit file. For more information on this feature, see the Debugging with GDB user

manual and the Debugging Dynamic Memory Usage Errors Using HP WDB white paper

at:

http://www.docs.hp.com/en/dev.html

Patches and Defect Fixes in HP WDB 5.9

The following defects are fixed in HP WDB 5.9:

• The disable command produces misleading information for multi-threaded

programs.

• The pxdb fails with an out of memory error message while reading files of size 2

GB.

• WDB incorrectly reports heap object registered with different size when an

application is compiled with +check=bounds:pointer to perform out of bounds

check.

• WDB incorrectly reports value of thread-local variable.

• The next command fails to step into a forked child process.

• WDB does not recognize pack core filenames with extensions other than .tar.Z.

If the application is compiled with +check=memory, it crashes while WDB attempts

to print the memory information.

• Batch RTC fails even when the output_dir command is set and the current

working directory does not have write permission.

• WDB is unable to perform Java debugging.