Title and Contents

Preface

What Is the Ladebug Debugger?

This documentation explains how to use the Compaq Ladebug debugger. The Ladebug debugger supports C, C++, and Fortran programming on: It also has limited support for Cobol and Ada.

It supports debugging simple programs, as well as situations involving multiple threads, multiple processes, core files, kernels, and remote systems.

The official Software Product Description is part of the Developers' Toolkit Software Product Description (SPD 44.36).

Obtaining a Ladebug Kit

Ladebug kits, manuals, and answers to the frequently asked questions (FAQ) are available from the following sources:

Intended Audience

This manual is intended for programmers with a basic understanding of one of the programming languages that the Ladebug debugger supports (C, C++, Fortran, COBOL, and Ada) and the Compaq Tru64 UNIX and Linux for Alpha operating systems.

Structure of This Document

This manual is organized as follows:

Related Documents

The following documents contain related information:

Reporting Problems

Send mail to Ladebug.Support@Compaq.com.

What to Report

Please provide the following information when you enter your problem report. Doing so will make it easier for us to reproduce and analyze your problem. If you do not provide this information, we may have to ask you for it. The Ladebug development team can use ftp to fetch sources and executables provided you can place them in an anonymous FTP area. If not, you may be asked to use another method.

Conventions

The following conventions are used in this manual:

Convention Meaning
% A percent sign (%) represents the C shell system prompt.
# A pound sign (#) represents the default superuser prompt.
UPPERCASE
lowercase
The Tru64 UNIX operating system differentiates between lowercase and uppercase characters. On the operating system level, you must type examples, syntax descriptions, function definitions, and literal strings that appear in text exactly as shown.
Ctrl/C This symbol indicates that you must press the Ctrl key while you simultaneously press another key (in this case, C).
monospaced text This typeface indicates a routine, partition, pathname, directory, file, or non-terminal name. This typeface is also used in interactive examples.
monospaced bold text In interactive examples, this typeface indicates input that you enter. In syntax statements and text, this typeface indicates the exact name of a command or keyword.
monospaced italic text Monospaced italic type indicates variable values, place holders, and function argument names.

In syntax definitions, monospaced italic text indicates non-terminal names. When a non-terminal name consists of more than one word, the words are joined using the underscore (_), for example, breakpoint_command.

italic text Italic type indicates book names or emphasized terms.
foo_bar
    : item1
    | item2
    | item3
A colon starts the syntax definition of a non-terminal name (in this example, foo_bar. Vertical bars separating items that appear in syntax definitions indicate that you choose one item from among those listed.
[] In syntax definitions, brackets indicate items that are optional.
option ;...
option ,...
option  ...
A set of three horizontal ellipses indicates that you can enter additional parameters, options, or values. A semicolon, comma, or space preceding the ellipses indicates successive items must be separated by semicolons, commas, or spaces.
setld(8) Cross-references to online reference pages include the appropriate section number in parentheses. For example, setld(8) indicates that you can find the material on the setld command in Section 8 of the reference pages. The man command % man 8 setld shows the reference page for this command.