Go to main content

Oracle® Solaris Modular Debugger Guide

Exit Print View

Updated: October 2019
 
 

Transition From adb and kadb to MDB

The transition from using the legacy adb(1) utility to using mdb(1) is relatively simple: MDB provides evolutionary compatibility for the adb syntax, built-in commands, and command-line options. MDB attempts to provide compatibility for all existing adb features, but it is not bug-for-bug compatible with adb. This appendix briefly discusses several features of adb that are not precisely emulated by MDB in order to guide users to the new functionality.

Command-Line Option Differences Between adb and MDB

MDB provides a superset of the command-line options recognized by adb. All the adb options are supported and have the same meaning as before. The /usr/bin/adb pathname is delivered as a link that invokes mdb(1), and automatically enables enhanced adb compatibility mode. Executing the /usr/bin/adb link is equivalent to executing mdb with the –o adb option, or executing ::set -o adb once the debugger has started.