JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Modular Debugger Guide     Oracle Solaris 11.1 Information Library
search filter icon
search icon

Document Information

Preface

1.  Modular Debugger Overview

2.  Debugger Concepts

3.  MDB Language Syntax

4.  Using MDB Commands Interactively

5.  Built-In Commands

6.  Execution Control

7.  Kernel Execution Control

8.  Kernel Debugging Modules

9.  Debugging With the Kernel Memory Allocator

10.  Module Programming API

A.  MDB Options

Summary of MDB Command-Line Options

Operands

Exit Status

Environment Variables

B.  Notes

C.  Transition From adb and kadb

D.  Transition From crash

Index

Operands

The following operands are supported:

object

Specifies an ELF format object file to examine. mdb provides the ability to examine and edit ELF format executables (ET_EXEC), ELF dynamic library files (ET_DYN), ELF relocatable object files (ET_REL), and operating system unix.X symbol table files.

core

Specifies an ELF process core file (ET_CORE), or an operating system crash dump vmcore.X file. If an ELF core file operand is provided without a corresponding object file, mdb will attempt to infer the name of the executable file that produced the core using several different algorithms. If no executable is found, mdb will still execute, but some symbol information may be unavailable.

suffix

Specifies the numeric suffix that represents a pair of operating system crash dump files. For example, if the suffix is 3, then mdb should examine the files unix.3 and vmcore.3. If these files do not exist, but vmdump.3 does exist, then a message displays telling you to first run the following command to uncompress the dump file.

# savecore -f vmdump.3

The string of digits is not interpreted as a suffix if an actual file of the same name is present in the current directory.