CPU Windows Index

From RAD Studio
Jump to: navigation, search

Go Up to Debug Windows Index

View > Debug Windows > CPU Windows

Allows you to select either Entire CPU or any individual CPU window for debugging a specific low-level aspect of an application, such as the contents of the program stack, registers or CPU flags, memory dumps, or assembly instructions disassembled from the application’s machine code. You can also invoke the Entire CPU view by pressing Ctrl+Alt+c while any IDE window has focus (the product must be in debug mode at the time).

The CPU windows are:

Each pane gives you a view into a specific low-level aspect of your running application.

Opening the Entire CPU View

To open the Entire CPU view during a debugging session, do any of the following:

  • Choose View > Debug Windows > CPU Windows > Entire CPU.
  • Press Ctrl+Alt+c while any IDE window has focus.
  • Right-click the Code Editor and choose Debug | View CPU from the context menu.

The CPU window also opens automatically whenever program execution stops at a location for which source code is unavailable. For example, the debugger cannot open the source file if you link a DLL (Windows) built with debug information but do not include its source file in your project, or if you place the source file in a directory not specified in your project.

Resizing the CPU Panes

You can customize the layout of the CPU windows by resizing the panes. Drag the pane borders within the window to enlarge or shrink the window to your liking.

If you want to move the panes around in the IDE, open them individually from the View menu so that they are Dockable.

Single Panes of the CPU Window Are Dockable

You can open a single pane of the CPU window (such as the Disassembly, Registers, or CPU Stack views) from the View > Debug Windows submenu.

  • A single pane becomes a titled dockable view that you can move around inside the IDE.
  • CPU panes opened individually have an additional context menu command (Dockable) that toggles this feature. When Dockable is not checked, the pane cannot be docked in the IDE but remains an independent window.

Auto Close for Windows and Files When You Exit Debug

By default, when you close the debugger, the IDE closes the CPU view and the Modules view along with any files that were implicitly opened during your debugging session. You can, however, specify windows that are to remain open when the debugger closes; your choices are CPU view, Modules view, and implicitly opened windows. On the Tools > Options > Debugger Options dialog box, use the Auto close views after debugging options.

See Also