HP 3000 Manuals HP 3000 Manuals
Product 900 Series HP 3000 Computer Systems System Debug Reference Manual HP Part No. 32650-90013 Printed in U.S.A. Printed Oct 1989 Edition Second Edition E1089
________________________________________________________________________ |The information contained in this document is subject to change | |without notice. | | | |HEWLETT-PACKARD MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS | |MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF | |MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard | |shall not be liable for errors contained herein or use of this | |material. | | | |Hewlett-Packard assumes no responsibility for the use or reliability | |of its software on equipment that is not furnished by Hewlett-Packard.| | | |This document contains proprietary information which is protected by | |copyright. All rights are reserved. No part of this document may be | |photocopied, reproduced, or translated to another language without the| |prior written consent of Hewlett-Packard Company. | ________________________________________________________________________ Copyright Æ 1989 by Hewlett-Packard Company Print History The following table lists the printings of this document, together with the respective release dates for each edition. The software version indicates the version of the software product at the time this document was issued. Many product releases do not require changes to the document. Therefore, do not expect a one-to-one correspondence between product releases and document editions. Edition Date Software Version --------------------------------------------------------------------------------------- First Edition November 1987 A.01.00 Update 1 July 1988 A.10.00 Second Edition October 1989 A.30.00 Documentation MapPreface System Debug Reference Manual (32650-90013) is written for the experienced programmer. It is a reference manual that provides information about System Debug. System Debug provides a family of low-level assembly language debugging tools for MPE XL (for both Native and Compatibility Mode code): * Debug * Dump Analysis Tool (DAT) * Standalone Analysis Tool (SAT) A certain level of knowledge is required to utilize System Debug. Specifically, familiarity with assembly code, procedure calling conventions, parameter passing conventions, and HP 3000 and HP Precision Architecture is assumed. This manual is organized into the following chapters and appendices: Chapter 1 Introduction contains an introductory overview of System Debug features and describes how to get started with the debugger. Chapter 2 User Interface describes the common user interface supported by System Debug. This chapter describes expressions, types, operators, operands, functions, variable macros, error handling, regular expressions, the history stack, and Control-Y handling. Chapter 3 System Debug Interfaces Commands & Intrinsics describes the commands and intrinsics (both CM and NM) that enable you to invoke System Debug either interactively or programmatically. Chapter 4 System Debug Command Specifications lists the System Debug commands in alphabetic order, complete with full syntax, parameter descriptions, and examples of use. Chapter 5 Symbolic Formatting Symbolic Access presents an overview of symbolic formatting and symbolic access functions. Chapter 6 System Debug Windows describes the System Debug screen windows. Basic window operations are introduced, and a typical screen display is presented. Each type of window is described, along with an explanation of each field within the window. Chapter 7 System Debug Window Commands lists the System Debug window commands, broken into logical groups. The window commands are then listed in alphabetical order, along with full syntax, parameter descriptions, and examples of use. Chapter 8 System Debug Standard Functions lists the predefined System Debug functions in alphabetical order, complete with full syntax, parameter descriptions, and examples of use. Chapter 9 Dump Analysis Tool (DAT) contains information on the Dump Analysis Tool (DAT). Chapter 10 Standalone Analysis Tool (SAT) contains information on the standalone Analysis Tool (SAT). Appendix A Patterns and Regular Expressions presents pattern matching and regular expressions. Appendix B Expression Diagrams contains System Debug expression diagrams. Appendix C Emulated/Translated CM Code describes CM Object Code Translation Appendix D Reserved Variables/Functions contains a full summary of all reserved variables and functions. Appendix E System Debug Command Summary contains a full System Debug command summary. Conventions UPPERCASE In a syntax statement, commands and keywords are shown in uppercase characters. The characters must be entered in the order shown; however, you can enter the characters in either uppercase or lowercase. For example: COMMAND can be entered as any of the following: command Command COMMAND It cannot, however, be entered as: comm com_mand comamnd italics In a syntax statement or an example, a word in italics represents a parameter or argument that you must replace with the actual value. In the following example, you must replace filename with the name of the file: COMMAND filename bold italics In a syntax statement, a word in bold italics represents a parameter that you must replace with the actual value. In the following example, you must replace filename with the name of the file: COMMAND(filename) punctuation In a syntax statement, punctuation characters (other than brackets, braces, vertical bars, and ellipses) must be entered exactly as shown. In the following example, the parentheses and colon must be entered: (filename):(filename) underlining Within an example that contains interactive dialog, user input and user responses to prompts are indicated by underlining. In the following example, yes is the user's response to the prompt: Do you want to continue? >> yes { } In a syntax statement, braces enclose required elements. When several elements are stacked within braces, you must select one. In the following example, you must select either ON or OFF: {ON } COMMAND {OFF} Conventions (continued) [ ] In a syntax statement, brackets enclose optional elements. In the following example, OPTION can be omitted: COMMAND filename [OPTION] When several elements are stacked within brackets, you can select one or none of the elements. In the following example, you can select OPTION or parameter or neither. The elements cannot be repeated. [OPTION ] COMMAND filename [parameter] [...] In a syntax statement, horizontal ellipses enclosed in brackets indicate that you can repeatedly select the element(s) that appear within the immediately preceding pair of brackets or braces. In the example below, you can select parameter zero or more times. Each instance of parameter must be preceded by a comma: [,parameter][...] In the example below, you only use the comma as a delimiter if parameter is repeated; no comma is used before the first occurrence of parameter: [parameter][,...] |...| In a syntax statement, horizontal ellipses enclosed in vertical bars indicate that you can select more than one element within the immediately preceding pair of brackets or braces. However, each particular element can only be selected once. In the following example, you must select A, AB, BA, or B. The elements cannot be repeated. {A} {B} |...| ... In an example, horizontal or vertical ellipses indicate where portions of an example have been omitted. Å In a syntax statement, the space symbol Å shows a required blank. In the following example, parameter and parameter must be separated with a blank: (parameter)Å(parameter) The symbol indicates a key on the keyboard. For example, RETURN represents the carriage return key or Shift represents the shift key. CTRLcharacter CTRLcharacter indicates a control character. For example, CTRLY means that you press the control key and the Y key simultaneously. Conventions (continued) base prefixes The prefixes %, #, and $ specify the numerical base of the value that follows: %num specifies an octal number. #num specifies a decimal number. $num specifies a hexadecimal number. If no base is specified, decimal is assumed. bits (bit:length) When a parameter contains more than one piece of data within its bit field, the different data fields are described in the format bits (bit:length), where bit is the first bit in the field and length is the number of consecutive bits in the field. For example, bits (13:3) indicates bits 13, 14, and 15: most significant least significant |--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--| | 0| | | | | | | | | | | | |13|14|15| |--|--|--|--|--|--|--|--|--|--|--|--|--|--|--|--| bits (0:1) bits (13:3)
![[]](../../pic3k/M010459/DMKDOCMP3c50.gif)