MPE Debug/Stack Dump Reference Manual : COPYRIGHT NOTICE [ MPE Debug/Stack Dump Reference Manual ] MPE/iX 5.0 Documentation
MPE Debug/Stack Dump Reference Manual
MPE Debug/Stack Dump Reference Manual
Printed in U.S.A.
HP Part No. 30000-90012
Edition 2nd
Printed Aug 1986
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 for incidental or
consequential damages in connection with the furnishing, performance 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.
Æ 1976-1978,1980,1983,1986
PREFACE
This manual describes two facilities that can be used to locate and
correct errors in programs run under control of the MPE operating system.
The two facilities are DEBUG and Stack Dump. The manual is part of a set
of manuals that describe operation of the Multiprogramming Executive
Operating System (MPE) for the HP 3000 Series II Computer System. The
manual plan on the next page illustrates the relation between this manual
(shaded box) and others in the set.
This manual is organized as follows:
Section I Contains an introduction to the DEBUG and Stack Dump
facilities.
Section II Describes the syntax of the DEBUG commands and the MPE
commands and intrinsics used by Stack Dump. The DEBUG
commands are listed in alphabetic order followed by the
Stack Dump commands and intrinsics; each command and
intrinsic is described formally in this section.
Section III Describes how to use the DEBUG facility, first for users
with standard capability followed by an expanded
description for users with privileged mode capability.
Section IV Describes how to use the Stack Dump facility, first in
case of abnormal program termination, and then
unconditionally.
Section V Describes the DEBUG error messages and the action to be
taken when each message is received.
Manual Map
CONVENTIONS USED IN THIS MANUAL
NOTATION DESCRIPTION
COMMAND Commands are shown in CAPITAL LETTERS. The names must
contain no blanks and be delimited by a non-alphabetic
character (usually a blank).
KEYWORDS Literal keywords, which are entered optionally but
exactly as specified, appear in CAPITAL LETTERS.
parameter Optional parameters, for which you may substitute a
value, appear in standard italics.
[ ] An element inside brackets is optional. Several
elements stacked inside a pair of brackets means the
user may select any one or none of these elements.
Example: [ A ]
[ B ] user may select A or B or
neither.
When brackets are nested, parameters in inner brackets
can only be specified if parameters in outer brackets or
comma place-holders are specified.
Example: [parm1[,parm2[,parm3] ] ]
may be entered as
parm1,parm2,parm3 or
parm1,,parm3 or
,,parm3 ,etc.
{ } When several elements are stacked within braces the user
must select one of these elements.
Example: { A }
{ B } user must select A or B or C.
{ C }
... An ellipsis indicates that a previous bracketed element
may be repeated, or that elements have been omitted.
user input In examples of interactive dialog, user input is
underlined.
Example: NEW NAME? ALPHA1
superscriptc Control characters are indicated by a superscriptc .
Example: Yc . (Press Y and the CNTL key
simultaneously.)
RETURN RETURN indicates the carriage return key.
MPE/iX 5.0 Documentation