The Apex Debugger extends the Force.com IDE plug-in for Eclipse and behaves similarly to debuggers available for other languages. Use it in sandbox orgs to root out the bugs in your Apex code. After you’ve set a breakpoint and started a debugging session, you can debug actions in your org that cause the line of code to execute.
Use the Apex Debugger to complete the following actions.
- Set breakpoints in Apex classes and triggers.
- View variables, including sObject types, collections, and Apex System types.
- View the call stack, including triggers activated by Apex Data Manipulation Language (DML), method-to-method calls, and variables.
- Interact with global classes, exceptions, and triggers from your installed managed packages. When you inspect objects that have managed types that aren’t visible to you, only global variables are displayed in the variable inspection pane.
- Complete standard debugging actions, including step into, over, and out, and run to breakpoint.
- Output your results to the Console window.