Document revision date: 30 March 2001

## OpenVMS Debugger Manual

Order Number: AA-QSBJD-TE

## April 2001

This manual explains the features of the OpenVMS Debugger for programmers in high-level languages and assembly language.

Revision/Update Information: This manual supersedes the OpenVMS Debugger Manual, Version 7.2.

Software Version: OpenVMS Alpha Version 7.3 OpenVMS VAX Version 7.3

Compaq Computer Corporation
Houston, Texas

© 2001 Compaq Computer Corporation

Compaq, VAX, VMS, and the Compaq logo Registered in the U.S. Patent and Trademark Office.

OpenVMS is a trademark of Compaq Information Technologies Group, L.P. in the United States and other countries.

Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States and other countries.

Intel is a trademark of Intel Corporation in the United States and other countries.

Motif, Open Software Foundation, OSF/1, and UNIX are trademarks of The Open Group in the United States and other countries.

All other product names mentioned herein may be the trademarks of their respective companies.

Confidential computer software. Valid license from Compaq 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.

Compaq shall not be liable for technical or editorial errors or omissions contained herein.

The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for Compaq products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty.

ZK4538

The Compaq OpenVMS documentation set is available on CD-ROM.

Contents | Index

## Preface

## Intended Audience

This manual is for programmers at all levels of experience. It covers all user interfaces of the OpenVMS Debugger:

- The command interface for terminals and workstations
- The Compaq DECwindows Motif for OpenVMS user interface for workstations
- The Microsoft Windows PC client interface

On VAX processors, you can use the debugger with programs written in the following VAX languages:

Ada | BASIC | BLISS | C
C++ | COBOL | DIBOL | Fortran
MACRO-32 | Pascal | PL/I | RPG II
SCAN |  |  |

On Alpha processors, you can use the debugger with programs written in the following Compaq languages:

Ada | BASIC | BLISS | C
C++ | COBOL | Fortran | MACRO-32 1
MACRO-64 | Pascal | PL/I |

1Note that MACRO-32 must be compiled with the AMACRO compiler.

The OpenVMS Debugger on OpenVMS Alpha systems can access all the extended memory made available by the 64-bit processing of the OpenVMS Alpha operating system. Hence, you can examine and manipulate data in the complete 64-bit address space.

The OpenVMS Debugger has been internationalized. For Asian users, the debugger's Compaq DECwindows Motif for OpenVMS, command line, and screen mode user interfaces can be used with multibyte characters.

You can use the debugger to debug code only in user mode. You cannot debug code in supervisor, executive, or kernel modes.

## Document Structure

This manual is organized as follows:

- Part 1 introduces the OpenVMS Debugger. Part 1 contains one chapter:
  - Chapter 1 introduces the debugger.
- Part 2 describes the debugger's command interface. Part 2 includes the following chapters:
  - Chapter 2 gets you started using the debugger.
  - Chapter 3 explains how to control and monitor program execution.
  - Chapter 4 explains how to examine and manipulate program data.
  - Chapter 5 explains how to control access to symbols in your program.
  - Chapter 6 explains how to control the display of source code.
  - Chapter 7 explains how to use screen mode.
- Part 3 describes the debugger's Compaq DECwindows Motif for OpenVMS user interface. Part 3 includes the following chapters:
  - Chapter 8 gives an overview of its Compaq DECwindows Motif for OpenVMS user interface features.
  - Chapter 9 explains how to prepare your program for debugging and then start and end a debugging session using the Compaq DECwindows Motif for OpenVMS user interface.
  - Chapter 10, which is organized by task, explains how to use the debugger via the Compaq DECwindows Motif for OpenVMS user interface.
- Part 4 describes the debugger's PC interface. Part 4 contains one chapter:
  - Chapter 11 gives an overview of the debugger's PC interface.
- Part 5 describes advanced debugging topics. Part 5 includes the following chapters:
  - Chapter 12, which is organized by task, explains how to use the debugger's Heap Analyzer.
  - Chapter 13 explains additional convenience features, such as key definitions and other customizations.
  - Chapter 14 explains some special cases, such as debugging optimized programs and multilanguage programs.
  - Chapter 15 explains how to debug multiprocess programs.
  - Chapter 16 explains how to debug vectorized programs (VAX only).
  - Chapter 17 explains how to debug tasking (multithread) programs.

- Part 6 is the debugger command dictionary, followed by the appendixes:
  - Appendix A lists the keypad-key definitions that are predefined by the debugger.
  - Appendix B identifies all of the debugger built-in symbols and logical names.
  - Appendix C identifies the debugger support for languages.
  - Appendix D contains the source code of the programs shown in the figures in Chapters 8, 9, and 10.

## Related Documents

The following documents may also be helpful when using the debugger.

Programming Languages

This manual emphasizes debugger usage that is common to all or most supported languages. For more information specific to a particular language, see:

- The debugger's online help system (see Section 2.1)
- The documentation supplied with that language, particularly regarding compiling and linking the program for debugging
- The VAX MACRO and Instruction Set Reference Manual or the MACRO--64 Assembler for OpenVMS AXP Systems Reference Manual for information about assembly-language instructions and the MACRO assembler

Linker Utility

For information about the linking of programs or shareable images, see the OpenVMS Linker Utility Manual.

Delta/XDelta Debugger

For information about debugging code in supervisor, executive, or kernel modes (that is, in other than user mode), see the OpenVMS Delta/XDelta Debugger Manual in the OpenVMS documentation set. This manual contains information about debugging programs that run in privileged processor mode or at an elevated interrupt priority level.

OpenVMS Alpha System-Code Debugger (Alpha Only)

On Alpha processors, see the OpenVMS Alpha Device Support: Developer's Guide for information on debugging Alpha operating system code. This manual describes how to create an Alpha device driver, activate the OpenVMS Alpha System-Code Debugger through the OpenVMS Debugger, and debug within the OpenVMS Alpha System-Code Debugger environment.

For information on the OpenVMS Alpha System-Code Debugger-specific commands, see the CONNECT and REBOOT commands in Part 6.

Compaq DECwindows Motif for OpenVMS

For general information about the Compaq DECwindows Motif for OpenVMS user interface, see the VMS DECwindows User's Guide.

For additional information about Compaq OpenVMS products and services, access the Compaq website at the following location:

    http://www.openvms.compaq.com/

## Reader's Comments

Compaq welcomes your comments on this manual. Please send comments to either of the following addresses:

Internet | openvmsdoc@compaq.com
Mail | Compaq Computer Corporation OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698

## How to Order Additional Documentation

Use the following World Wide Web address to order additional documentation:

    http://www.openvms.compaq.com/

If you need help deciding which documentation best meets your needs, call 800-282-6672.

## Conventions

VMScluster systems are now referred to as OpenVMS Cluster systems. Unless otherwise specified, references to OpenVMS Clusters or clusters in this document are synonymous with VMSclusters.

In this manual, every use of DECwindows and DECwindows Motif refers to Compaq DECwindows Motif for OpenVMS software.

This manual contains many figures showing the DECwindows Motif user interface to the debugger. Because the display configuration of this interface is customizable, these figures may not exactly picture the appearance of debugger displays on your system.

The examples in this manual have not been updated to reflect the fact that the OpenVMS Debugger on OpenVMS Alpha systems can access all the extended memory made available by the 64-bit processing of the OpenVMS Alpha operating system. You should note that hexadecimal addresses are 16-digit numbers on Alpha and 8-digit numbers on VAX. For example,

    DBG> EVALUATE/ADDRESS/HEX %hex 000004A0
    00000000000004A0
    DBG>

The following conventions are also used in this manual:

Ctrl/ x | A sequence such as Ctrl/ x indicates that you must hold down the key labeled Ctrl while you press another key or a pointing device button.
PF1 x or GOLD x | A sequence such as PF1 x or GOLD x indicates that you must first press and release the key labeled PF1 or GOLD and then press and release another key or a pointing device button. GOLD key sequences can also have a slash (/), (-), or underscore (_) as a delimiter in EVE commands.
`[Return]` | In examples, a key name enclosed in a box indicates that you press a key on the keyboard. (In text, a key name is not enclosed in a box.) In the HTML version of this document, this convention appears as brackets, rather than a box.
... | A horizontal ellipsis in examples indicates one of the following possibilities: Additional optional arguments in a statement have been omitted. The preceding item or items can be repeated one or more times. Additional parameters, values, or other information can be entered.
. . . | A vertical ellipsis indicates the omission of items from a code example or command format; the items are omitted because they are not important to the topic being discussed.
( ) | In command format descriptions, parentheses indicate that you must enclose the options in parentheses if you choose more than one.
[ ] | In command format descriptions, brackets indicate optional choices. You can choose one or more items or no items. Do not type the brackets on the command line. However, you must include the brackets in the syntax for OpenVMS directory specifications and for a substring specification in an assignment statement.
| | In command format descriptions, vertical bars separate choices within brackets or braces. Within brackets, the choices are optional; within braces, at least one choice is required. Do not type the vertical bars on the command line.
{ } | In command format descriptions, braces indicate required choices; you must choose at least one of the of the items listed. Do not type the braces on the command line.
bold text | This typeface represents the introduction of a new term. It also represents the name of an argument an attribute, or a reason.
italic text | Italic text indicates important information, complete titles of manuals, or variables. Variables include information that varies in system output (Internal error number), in command lines (/PRODUCER= name), and in command parameters in text (where dd represents the predefined code for the device type).
UPPERCASE TEXT | Uppercase text indicates a command, the name of a routine, the name of a file, or the abbreviation for a system privilege.
    Monospace text
| Monospace type indicates code examples and interactive screen displays. In the C programming language, monospace type in text identifies the following elements: keywords, the names of independently compiled external functions and files, syntax summaries, and references to variables or identifiers introduced in an example.
- | A hyphen at the end of a command format description, command line, or code line indicates that the command or statement continues on the following line.
numbers | All numbers in text are assumed to be decimal unless otherwise noted. Nondecimal radixes---binary, octal, or hexadecimal---are explicitly indicated.

## Part 1
Introduction to the Debugger

This part introduces the Debugger.

## Chapter 1
Introduction to the Debugger

This chapter briefly describes the command interface of the OpenVMS Debugger, and provides the following information:

- An overview of debugger features
- Instructions to compile and link your program for debugging
- Instructions to start and end a debugging session
- A list of the debugger commands grouped by function

For a tutorial introduction to basic debugging tasks, see Chapter 2.

## 1.1 Overview of the Debugger

The OpenVMS Debugger is a tool to locate run-time programming or logic errors, also known as bugs, in a program that has been compiled and linked successfully but does not run correctly. For example, the program might give incorrect output, go into an infinite loop, or terminate prematurely.

By using the OpenVMS Debugger, you can locate program bugs by observing and manipulating the program interactively as it executes. Debugger commands enable you to:

- Control and observe execution of the program
- Display and browse through the source code of the program to identify instructions and variables worth scrutiny
- Suspend program execution at specified points in order to monitor changes in variables and other program entities
- Change the value of a variable and, in some cases, test the modification without having to edit the source code, recompile, and relink
- Trace the execution path of the program
- Monitor exception conditions and language-specific events

These are basic debugging techniques. After locating program errors, you can edit the source code and compile, link, execute, and test the corrected version.

As you use the debugger and its documentation, you will discover and develop variations on the basic techniques. You can also customize the debugger for your own needs. Section 1.1.1 summarizes the features of the OpenVMS Debugger.

Note The kernel and main debugger communicate through global sections. The main debugger communicates with up to eight kernel debuggers through a 65-page (VAX) or 65-pagelet (Alpha) global section (65*512 bytes on either platform). Therefore, you might need to increase the system parameters GBLPAGES and GBLSECTIONS. For example, if 10 users use the debugger simultaneously, the debugger requires 10 global sections using a total of 650 global pages or pagelets.

Note Each user needs a PRCLM quota sufficient to create an additional subprocess for the debugger, beyond the number of processes needed by the program. BYTLM, ENQLM, FILLM, and PGFLQUOTA are pooled quotas. You may need to increase these quotas to account for the debugger subprocess as follows: You should increase each user's ENQLM quota by at least the number of processes being debugged. You might need to increase each user's PGFLQUOTA. If a user has an insufficient PGFLQUOTA, the debugger may fail to activate or may cause "virtual memory exceeded" errors during execution. You might need to increase each user's BYTLM and FILLM quotas. The debugger requires sufficient BYTLM and FILLM quotas to open each image file being debugged, the corresponding source files, and the debugger input, output, and log files. To increase these quotas, you can run SYS$SYSTEM:AUTHORIZE.EXE to adjust parameters in SYSUAF.DAT.

### 1.1.1 Functional Features

Programming Language Support

On VAX processors, you can use the debugger with programs written in the following VAX languages:

Ada | BASIC | BLISS | C
C++ | COBOL | DIBOL | Fortran
MACRO-32 | Pascal | PL/I | RPG II
SCAN |  |  |

On Alpha processors, you can use the debugger with programs written in the following Compaq languages:

Ada | BASIC | BLISS | C
C++ | COBOL | Fortran | MACRO-32 1
MACRO-64 | Pascal | PL/I |

1Note that MACRO-32 must be compiled with the AMACRO compiler.

The debugger recognizes the syntax, data types, operators, expressions, scoping rules, and other constructs of a supported language. You can change the debugging context from one language to another (with the SET LANGUAGE command) during a debugging session.

Symbolic Debugging

The debugger is a symbolic debugger. You can refer to program locations by the symbols used in your program---the names of variables, routines, labels, and so on. You can also specify explicit memory addresses or machine registers if you choose.

Support for All Data Types

The debugger recognizes the data types generated by the compilers of all supported languages, such as integer, floating-point, enumeration, record, array, and so on, and displays the values of each program variable according to its declared type.

Flexible Data Format

With the debugger, you can enter and display a variety of data forms and data types. The source language of the program determines the default format for the entry and display of data. However, you can select other formats as needed.

Starting or Resuming Program Execution

Once the program is under control of the debugger, you can start or resume program execution with the GO or STEP command. The GO command causes the program to execute until specified events occur (the PC points to a designated line of code, a variable is modified, an exception is signaled, or the program terminates). You can use the STEP command to execute a specified number instructions or lines of source code, or until the program reaches the next instruction of a specified class.

Breakpoints

You can set a breakpoint with the SET BREAK command, to suspend program execution at a specified location in order to check the current status of the program. You can also direct the debugger to suspend execution when the program is about to execute an instruction of a specific class. You can also suspend execution when certain events occur, such as exceptions and tasking (multithread) events.

Tracepoints

You can set a tracepoint with the SET TRACE command, to cause the debugger to report each time that program execution reaches a specified location (that is, each time the program counter (PC) references that location). As with the SET BREAK command, you can also trace the occurrence of classes of instructions and monitor the occurrence of certain events, such as exceptions and tasking (multithread) events.

Watchpoints

You can set a watchpoint with the SET WATCH command to cause the debugger to suspend program execution whenever a particular variable (or other specified memory location) has been modified, at which point the debugger reports the old and new values of the variable.

Manipulation of Variables and Program Locations

You can use the EXAMINE command to determine the value of a variable or memory location. You can use the DEPOSIT command to change that value. You can then continue execution of the program to determine the effect of the change without having to recompile, relink, and rerun the program.

Evaluation of Expressions

You can use the EVALUATE command to compute the value of a source-language expression or an address expression in the syntax of the language to which the debugger is currently set.

Control Structures

You can use logical control structures (FOR, IF, REPEAT, WHILE) in commands to control the execution of other commands.

Shareable Image Debugging

You can debug shareable images (images that are not directly executable). The SET IMAGE command enables you to access the symbols declared in a shareable image (that was compiled and linked with the /DEBUG qualifiers).

Multiprocess Debugging

You can debug multiprocess programs (programs that run in more than one process). The SHOW PROCESS and SET PROCESS commands enable you to display process information and to control the execution of images in individual processes.

Task Debugging

You can debug tasking programs (also known as multithread programs). These programs use Compaq POSIX Threads Library or POSIX 1003.1b services, or use language-specific tasking services (for example, Ada tasking programs). The SHOW TASK and SET TASK commands enable you to display task information and to control the execution of individual tasks.

Vector Debugging (VAX Only)

On VAX processors, you can debug vectorized programs, that is, programs that use VAX vector instructions. You can control and monitor execution at the vector instruction level, examine and deposit vector instructions, manipulate the contents of vector registers, use a mask to display specific vector elements, and control synchronization between the scalar and vector processors.

Terminal and Workstation Support

The debugger supports all VT-series terminals and MicroVAX workstations.

Next | Contents | Index

| privacy and legal statement |
4538PRO.HTML