HP WDB 5.5 Release Notes

Introduction

What is New in This Release

Chapter 1

The info thread [thread-id] command displays a list of known threads. If a thread-id is provided, the

command displays extended information on the thread.

— info mutex [mutex-id]

The info mutex [mutex-id] command displays a list of known mutexes. If a mutex-id is provided, the

command displays extended information on the mutex.

— info condvar [condvar-id]

The info condvar [condvar-id] command displays a list of known condition variables. If condvar-id is

provided, the command displays extended information on the condition variables.

— info rwlock [rwlock-id]

The info rwlock [rwlock-id] command displays a list of known read-write lock. If rwlock-id is provided,

the command displays extended information on the read-write lock.

NOTE

— The commands, info mutex, info condvar, info thread, and info rwlock work only if

thread-check is set to on.

— The enhanced thread functionality is supported only on HP-UX 11i version 2 and later on both

PA-RISC and Integrity systems.

— For PA-RISC 32-bit applications, the enhanced thread functionality does not work if the application

is built using default linker options.

To enable this functionality, you must enable the dynamic library lookup through the

LD_LIBRARY_PATH environment variable using the following command on the HP-UX prompt:

# chatr +s enable <PA32-bitApp>

• Support for memory checking analysis for user defined memory management routines

Many user applications have their own memory management routines. These custom allocator routines are either user

defined or sometimes wrappers to the default memory management routines. Memory checking features has been

extended for user defined memory management routines. Memory leak, profile of heap memory or memory errors can be

obtained for user defined memory routines.

Limitations of the memory checking analysis feature:

— This feature doesnot work in batch mode.

— This feature routes to default memory routines instead of calling user defined memory routines to obtain memory

analysis.

• Enhanced heap checking

The high water mark records the number of times the brk() value changes. The following commands are supported:

— info heap high-mem: Displays the number of times brk() value changes for a given run.

— info heap high-mem X_number: Stops when brk() value has moved X_number of times.

Limitation

— High-mem commands are not supported in batch mode.

— This feature assumes that an application has a deterministic memory allocation pattern from one run to another.