HP WDB 6.
© Copyright 2013, 2014 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.
Contents HP secure development lifecycle......................................................................4 1 HP WDB 6.5 Release Notes........................................................................5 Announcement.........................................................................................................................5 What is new in this version........................................................................................................
HP secure development lifecycle Starting with HP-UX 11i v3 March 2013 update release, HP secure development lifecycle provides the ability to authenticate HP-UX software. Software delivered through this release has been digitally signed using HP's private key. You can now verify the authenticity of the software before installing the products, delivered through this release. To verify the software signatures in signed depot, the following products must be installed on your system: • B.11.31.
1 HP WDB 6.5 Release Notes Announcement (WDB) HP Wildebeest Debugger 6.5 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 6.5.
• HP WDB reports false leak for fwrite for memory debugging with RTC. • HP WDB does not show all the options for ptype of template functions. Known problems and workarounds This section describes known problems and the suggested workarounds in this release of HP WDB. • The find command does not search the entire memory. The HP WDB find command does not search the pattern in the entire memory address range starting from 0x0 to 0xff..ff.
Batch mode thread debugging • During the execution of advanced thread checking for applications that fork, in the interactive mode, the following message appears if the GDB follows the child: Pthread analysis file missing! This error message appears because the thread-error information for the forked process is not available. However, if the forked process exec() s another binary, the thread-error information is available for the exec-ed binary.
Mixed mode debugging The following are not supported for mixed mode debugging: • Placing a breakpoint on a PA-RISC library. • Listing the arguments (using the info args command) for a selected PA-RISC frame during corefile debugging. Alternatively, the disassembly instructions or runtime conventions can be examined to identify the locations of the arguments and the values at these locations can be displayed using the print or x command.
Filesets The HP WDB product contains the following components: • WDB: Runtime contains one fileset • WDB-DOC: Documentation contains one fileset • WDB-MAN: Manuals contains one fileset • SENTINEL: Run time monitoring and debugging tool NOTE: DEBUG-PRG is a co-requisite fileset for HP WDB and is automatically selected during installation.
Table 2 lists the documents available for HP WDB. Table 2 HP WDB Documentation Document Format Location Debugging with GDB PDF /opt/langtools/wdb/doc/gdb.pdf Emacs: /opt/langtools/wdb/doc/gdb.info (Copy the files to your info directory first.) GDB Quick Reference Card PDF /opt/langtools/wdb/doc Getting Started with HP WDB HTML /opt/langtools/wdb/doc/html/wdb/C/ GDBtutorial.html XDB to WDB Transition Guide HTML /opt/langtools/wdb/doc/index.
2 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
