Debugging Core Files Using HP WDB (5900-1573; WDB 6.2; January 2011)

Related Information
The following table lists the documentation available for HP WDB.
LocationDocument
/opt/langtools/wdb/doc/gdb.pdfDebugging with GDB
/opt/langtools/wdb/doc/refcard.pdfGDB Quick Reference Card
/opt/langtools/wdb/doc/html/wdb/C/GDBtutorial.htmlGetting Started With HP WDB
/opt/langtools/wdb/doc/index.htmlWDB GUI Online Help
/opt/langtools/wdb/doc/html/wdbgui/C/HP WDB GUI Documentation
gdb(1)GDB manpage
For the most current HP WDB documentation, see the HP WDB Technical Resources
website at:
http://www.hp.com/go/wdb
Introduction
HP Wildebeest Debugger (WDB) is an HP-supported implementation of the open source
debugger GDB. Apart from performing the normal debugging functions, it also enables
you to debug core files and analyze the process state of an application.
HP WDB debugs core files that are created by source-level 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
operating systems.
What Is a Core File?
A core dump is an abnormal termination of a program. The most common types of
programming errors that can cause a core dump include program aborts, memory
violations, bus errors, and illegal instructions. When a core dump occurs during the
execution of a program, the core file, core, is created in the working directory of the
terminated process. This core file reflects the memory image of the terminated process.
You can use the information in a core file to debug an abnormally-terminated program
and analyze the causes for the core dump.
Causes for a Core Dump
When a kernel encounters an un-handled signal, it creates a core file for that process.
Alternately, the user can force a core dump to create a core file (through WDB or by
using gcore).
6