About This Document

This manual describes using the Intel® Debugger on Linux* and Mac OS* systems, including preparing your program and starting the debugger, using debugger commands to accomplish various tasks, information about viewing data, viewing the call stack, controlling execution and locating problems, as well as detailed, advanced information.

Organization

The manual is organized as follows:

Part I contains a quick introduction to the Debugger

Part II contains information to help you make expert use of the Debugger

Part III contains advanced reference information

The appendixes contain the following information:

the Debugger variables

the Debugger aliases

the corefile_listobj.c example

the array navigation example

Intended Audience

This manual is intended for programmers who have a working knowledge of one of the programming languages that Intel IDB supports (C, C++, Fortran).

Notation Conventions

The following conventions are used in this manual:

Convention	Meaning
`%`	A percent sign represents the C shell system prompt.
`#`	A pound sign represents the default super-user prompt.
UPPERCASE lowercase	The 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.