Go to main content

Oracle® Solaris Modular Debugger Guide

Exit Print View

Updated: December 2019

MDB Operands

The following operands are supported:


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.


Specifies an ELF process core file (ET_CORE), or an operating system crash dump vmcore.X or vmcore.3file. 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.


Specifies the numerical suffix representing a number of operating system crash dump files. For example, if the suffix is 3, then mdb should examine the files vmcore.3 and all vmcore-<section>.3 files. If these files do not exist, but vmdump.3 does exist, then a message is printed indicating that savecore –f vmdump.3 must be run first in order to uncompress the dump file. If vmcore.3 exists and some of the vmcore-<section>.3 files referenced by vmcore.3 do not exist, the mdb loads the files and issues warning that the virtual memory image will not be complete. The string of digits are not interpreted as a suffix if an actual file of the same name is present.