About This Manual

What Is the Ladebug Debugger?

Ladebug is a symbolic source-level debugger with a choice of command line or graphical user interface.

Ladebug provides extensive support for debugging programs written in C, C++, and Fortran (77 and 90) for the following operating systems:

• HP Tru64 UNIX systems
• Linux for Alpha systems

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

Obtaining a Ladebug Kit

• The Ladebug website:

  http://www.compaq.com/ladebug

• The Developers' Toolkit website:

  http://www.tru64unix.compaq.com/dtk/

Audience

Organization

• Part I contains a quick introduction to the debugger.
  • Chapter 1 contains all the information you need to make simple use of the debugger.
• Part II contains most of the information you need to make expert use of the debugger.
  • Chapter 2 describes preparing your program for debugging.
  • Chapter 3 describes starting the debugger.
  • Chapter 4 describes giving commands to the debugger.
  • Chapter 5 describes the context for executing commands.
  • Chapter 6 describes running your program under debugger control.
  • Chapter 7 describes locating the site of a problem.
  • Chapter 8 describes how to examine the code, the data, and previously obtained information.
  • Chapter 9 describes modifying the process.
  • Chapter 10 describes continuing execution of the process.
  • Chapter 11 describes snapshots as an undo mechanism.
  • Chapter 12 describes debugging optimized code.
  • Chapter 13 describes support limitations.
• Part III contains advanced reference information.
  • Chapter 14 describes preparing a program for debugging.
  • Chapter 15 describes the debugger's syntax and grammar.
  • Chapter 16 describes debugging core files.
  • Chapter 17 describes kernel debugging and remote kernel debugging using the kdebug debugger.
  • Chapter 18 describes machine-level debugging.
  • Chapter 19 describes parallel debugging.
• The appendixes contain the following information:
  • Appendix 1 describes the debugger variables.
  • Appendix 2 describes the debugger aliases.
  • Appendix 3 contains the corefile_listobj.c example.
  • Appendix 4 contains the array navigation example.

Related Documentation

• Alpha Architecture Handbook
• Alpha Architecture Reference Manual
• Compaq Fortran Language Reference Manual
• Developing Ada Programs on Tru64 UNIX Systems
• The Annotated C++ Reference Manual, by Margaret E. Ellis and Bjarne Stroustrup, 1990, Addison-Wesley Publishing Company
• Reference pages:
  • ladebug(1)
  • cxx(1) for C++
  • cc(1) for C
  • ada(1) for Ada
  • cobol(1) for COBOL
  • f77(1) for Fortran 77
  • f90(1) for Fortran 90

Reporting Problems

What to Report

• A description of the problem. The clearer and more detailed the description, the easier it will be for us to reproduce and analyze your problem.
• A transcript of the debugger output. You can obtain this by using the record io Ladebug command or by using the script(1) system command.
• Operating system and version information. The output of uname -a is best.
• Ladebug version information. The version number is in the welcome banner that displays when you invoke the debugger. You can also obtain the version number by invoking the debugger with the ladebug -V command.
• The smallest source code example possible; build instructions (a Makefile is preferable); source languages, compiler versions, and so forth; and a pointer to a tar file containing sources or binaries that reproduce the problem. To obtain compiler versions, you can use the -V option if your compiler supports it (see the reference page for your compiler). Alternatively, you can generate the output of /usr/sbin/setld -i showing the installed compiler subsets.
• The exact Ladebug commands that cause the problem to occur.
• Any other information that you think would be helpful.

The Ladebug development team can use ftp to fetch sources and executables if you can place them in an anonymous FTP area. If not, you may be asked to use another method.

Conventions

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.

In this manual, some examples show Ladebug version numbers as "Version n". When you use the debugger, the actual version numbers appear on your screen.