Defects Fixed in HP WDB 3.0.01

HP WDB correctly unwinds beyond alloca frames and displays a full stack trace when debugging core files.
While debugging a core file, HP WDB searches for shared libraries and displays a warning message for each shared library it is unable to locate, not just for the first shared library.
Some earlier versions of HP WDB were unable to handle stripped core files. This has been fixed. Now, you will be able to get a stack trace and disassembly of the program counter at the point where the program stopped.
HP WDB no longer aborts when trying to print a variable or set a break point in a function that is located in a shared library compiled with +objdebug.The failure often seemed dependent on the names of the variables and functions. HP WDB now properly accesses these shared library symbols.
Several defects fixed in the info registers command:
- While debugging a core file, the info registers command always gave incorrect value for register 3.
- When debugging 2.0 Narrow core files, HP WDB’s info registers command no longer prints 32-bit values instead of 64-bit values for registers. HP WDB now prints the true 64-bit wide register values where they are appropriate.
- The info registers command now takes into account the screen width, controlled by the set width command, to determine the number of registers to display on each row. If the width has not been set, HP WDB uses the termcap database together with the value of the TERM environment variable and the stty cols setting or the COLUMNS environment variable to determine the screen width.

Defects Fixed in HP WDB 3.0.01

Technical documentation

» Table of Contents