Introduction

SUPER-UX DEBUG MONITOR GUIDE

This document describes the SUPER-UX kernel debugger. The debugger can be used to debug the SUPER-UX kernel when functions such as drivers are added.

This guide consists of the following chapters.

• Chapter 1, Kernel Debugger (KDB), gives an overview of the kernel debugger and its various functions.

• Chapter 2, Activating KDB, describes how to activate the debugger by various methods.

• Chapter 3, Operation, discusses kernel debugger command format, address specification, and operation.

• Chapter 4, Commands, lists the debugger commands and outlines their uses.

• Chapter 5, Error Messages, covers the kernel debugger error messages, the cause, and action to take to correct the situation.

CONVENTIONS

The following conventions are used throughout this document.

• Names of keys are printed as they appear on a standard keyboard, Ctrl, Back Space, and so on.

• Keys to be pressed and text to be entered or typed appear in boldface type. For example, an instruction to press the Return key would appear as "press Return." Also appearing in boldface are any command strings that must be entered exactly as they appear. For example,
  re practice

• The term "enter" ("entering," etc.) always refers to the two-step process of typing the given command or character string, and then pressing the Return key. For example, the statement "Enter justify" means to type justify and then press the Return key. In these cases, the system does not respond to the command or character string until you press the Return key.

• "Press" or "type," on the other hand, indicate simply to press or type the stated keys or characters without pressing the Return key.

• Text strings enclosed in brackets are optional. In the following example, options may or may not be included after the command.
  dir [options]

• Variable information is printed in italics. For example, to enter the command string
  pr /usr/filename

  filename is variable information.

• Options (-p, -n, etc.), reserved words (#define, if, while, goto, etc.), arguments, function names, and keywords appear in boldface type.

• File names and directories remain as standard text.

RELATED DOCUMENTS

See the following documents for related information:

• SUPER-UX System Administrator's Guide

• SUPER-UX Cluster System Administrator's Guide

• SUPER-UX System Administrator's Reference Manual

• SUPER-UX System Design Guide

REMARKS

This document corresponds to SUPER-UX Release 9.2 or later and describes the function of the following program product.

• U92001-01-GxxE SUPER-BASE (SUPER-UX Basic Software)

xx represents a group number of each system group.

MAJOR CHANGES IN THIS RELEASE

The following table lists the major changes in upgrading from Release 9.1 to 9.2.

The deleted portions are indicated by the number of the chapter, section, or subsection of the previous version.