Debugger Options

From Appmethod Topics
Jump to: navigation, search

Go Up to Tools Options Dialog Box

Tools > Options > Debugger Options

Use this page to set general debugger options for the IDE.

Item Description

Integrated Debugging

Activates the Integrated Debugger. Default is On.

Map TD32 keystrokes on run

Allows you to use the keystrokes from TD32 (Turbo Debugger 32-bit) in the IDE. When this option is checked, the TD32 keymapping will be active anytime a debug session is in progress. Note that if this option is selected, the Mark buffers read-only on run option is automatically checked as well and cannot be unchecked.

Mark buffers read-only on run

Marks all editor files, including project and workgroup files, read-only when the program is run. When this option is selected, it will not change the attributes of the files after the program terminates. If the file was not marked read-only before running the program, the product will change the attributes of the file back to their original configuration after the program terminates.

Rearrange editor local menu on run

Moves the Debugger area of the Code Editor context menu to the top when you run a program from the IDE, for easier access the Debugger commands. Display the Code Editor context menu by right-clicking anywhere in the Code Editor window.

Allow side effects and function calls in new watches

Causes the watch to be evaluated even if doing so would cause side effects or require function calls. Can be set for individual watches using the Watch Properties dialog box. By default, this option is not set. See also E2382 Side effects are not allowed (C++).

Prompt to rebuild projects modified while debugging

Enables the dialog box that asks whether you want to rebuild a project that was modified during debugging. When this option is disabled, the debugger does not prompt and does not rebuild. Default is On.

Auto close views after debugging

Closes specific debug views or all files that you did not explicitly open. Choose from the following:

  • Files implicitly opened while debugging - When you exit the debugger, closes all files that you did not explicitly open. If the debugger opened a file implicitly, the file is closed automatically at the end of the debug session if it has not been changed. Files that have been edited or for which you have set a breakpoint are not closed automatically.
  • CPU view - Closes the CPU Windows when you exit the debugger.
  • Modules view - Closes the Modules Window when you exit the debugger.

Registered Debuggers

Lists the available debuggers, including:

  • Embarcadero Win32 Debugger - the default native debugger (can be used for remote debugging as well as local debugging)
  • Embarcadero Win64 Debugger - the debugger for 64-bit Windows applications
    For a Win32 development system, the Win64 debugger runs remotely on the target Win64 system.
    For a Win64 development system, the Win64 debugger runs either locally or remotely on the Win64 host.
  • Embarcadero Mac OS X Debugger - the debugger for apps compiled for either Mac OS X or the iOS Simulator running on the Mac.
    The Mac OS X Debugger runs on the Mac, and it is also the debugger for the iOS Simulator.
  • Embarcadero iOS32 Device Debugger - the debugger for 32-bit iOS applications compiled for the iOS Device - 32 bit target platform
    The iOS32 Device Debugger runs on the iOS device.
  • Embarcadero iOS64 Device Debugger - the debugger for 64-bit iOS applications compiled for the iOS Device - 64 bit target platform
    The iOS64 Device Debugger runs on the iOS device.
  • Embarcadero Android Debugger - the debugger for Android applications compiled for the Android device.
    The Android Debugger runs on the Android device when the Android device is the target platform.

When you use the multi-device debuggers, you interact with the integrated debugger in the IDE just as you do for Win32 debugging. For more information, see Debugging Multi-Device Applications.

The current active debugger is shown in boldface. (The debugger is determined by the current platform selection in the Target Platforms node on the Project Manager.)

Child Pages

See Also