HP WDB 5.
© Copyright 2007 Hewlett-Packard Development Company, L.P Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained in this document is subject to change without notice.
Table of Contents HP WDB 5.7 Release Notes.............................................................................................7 Announcement.......................................................................................................................................7 What Is New in This Version..................................................................................................................7 What is New in This Version of HP WDB for Integrity Systems........................
List of Tables 1 2 3 4 Dependent Library Routines for Run Time Checking using WDB...............................................13 HP WDB Installation.....................................................................................................................15 Supported Systems for PA-RISC Core File Debugging.................................................................17 HP WDB Documentation........................................................................................................
HP WDB 5.7 Release Notes Announcement HP Wildebeest Debugger (WDB) 5.7 is an HP-supported implementation of the open source debugger GDB. It supports source-level debugging of programs written in HP C, HP aC++, and Fortran 90 on Itanium®-based systems running HP-UX 11i v2 or HP-UX 11i v3, and HP 9000 systems running HP-UX 11i v1, HP-UX 11i v2, or HP-UX 11i v3. This document discusses the most recent product information for HP WDB 5.
available. In such cases, the debugger reports that the value of the local variable is not available because of optimization. The debugger displays the current code address, which is used in the attempt to recover the value of the variable. If the variable is optimized completely out of existence, the debugger reports the corresponding message. Optimization of code results in the reordering of the instructions and the source line-numbers.
HP WDB 5.7 provides the following support for debugging macros: • Displaying Macro Definitions HP WDB 5.7 provides the following commands to display macro definitions: — show macro or info macro Displays the macro definition, source file name, and the line number. — macro expand Expands the macro and the parameters in the macro. If there are any parameters in the macro, they are substituted in the macro definition when the definition is displayed.
HP WDB 5.7 supports the following commands to print the execution path entries in the current frame, or in the current thread: • info exec-path [start_index] [end_index] (aliased to info ep) Lists all the local execution path entries in the current frame. The [start_index]and [end_index] indicate the range of table indexes (execution path entries) that must be displayed. If [end_index] is not specified, the debugger displays the complete table of execution path entries, starting from [start_index].
Automatic Preloading of librtc.[sl|so] with the New +mem_check Option for the chatr Command The new +mem_check option for the chatr command enables you to automatically preload the librtc.[sl|so] runtime library. In addition to automatically preloading the librtc.[sl|so] library, it also maps the shared library as private. This enhancement simplifies the current method of explicitly preloading the appropriate librtc.[sl|so] library, by using the LD_PRELOAD environment variable.
NOTE: To attach and find leaks for PA-32 applications from the start-up, the environment variable RTC_INIT should be set to on in addition to preloading the librtc.[sl|so] library before starting the application, as follows: $ RTC_INIT=on If RTC_INIT is turned on, librtc.[sl|so] starts recording heap information for PA–32 process, by default. Hence, you must set this environment variable only when memory debugging is required, and you must not export this environment variable for shell.
• • • • • • • • • • • • • • • • • • • Thread safety issues and heap corruption issues occur in an RTC function, rtc_split_special_region. Obsolete message text is displayed on attach failure with +Oprofile=collect executables. When GDB attaches to HP Caliper, it alters the behavior of the target. GDB erroneously display a warning message for pre-init mmap blocks. The makefiles and configure scripts must be updated to remove old librtc.a and librtc64.a builds.
Table 1 Dependent Library Routines for Run Time Checking using WDB (continued) time unlink uwx_self_copyin strchr uwx_step uwx_init perror shmctl write strcmp shl_get close dlgetname environ fork getpagesize uwx_self_init_context pthread_getschedparam uwx_self_init_info strstr uwx_register_alloc_cb uwx_register_callbacks uwx_self_lookupip The Run Time Checking (dynamic memory, libraries, and pthreads checking) in WDB is dependent on the semantics and the standard behavior of these library
The debugger displays the following error message while attempting to attach to such a process: Attaching to process failed. Hint: Check if this process is already being traced by another gdb or other ttrace tools like caliper and tusc. Hint: Check whether program is on an NFS-mounted file-system. If so,you will need to mount the file system with the "nointr" option with mount(1) or make a local copy of the program to resolve this problem.
NOTE: DEBUG-PRG and SENTINEL are co-requisite filesets for HP WDB and are automatically selected during installation. The WDB GUI product contains the following sub-products: • WDB-GUI-RUN: Runtime contains one fileset • WDB-GUI-HELP: Help contains one fileset • WDB-GUI-MAN: Manuals contain one fileset HP WDB GUI requires the HP WDB product. If HP WDB is not already installed, it is automatically selected during installation.
Table 3 Supported Systems for PA-RISC Core File Debugging Type of core files produced Supported systems for debugging Core files produced by 32–bit executables Any PA-RISC 1.1 or PA-RISC 2.0 system with an HP-UX version greater than or equal to the HP-UX version on the system where the core file was produced. Core files produced by 64–bit executables Other PA-RISC 2.0 systems with HP-UX versions greater than or equal to the HP-UX version on the system where the core file was produced.
