Breakpoints tab
The purpose of the breakpoints tab is to specify the load modules to be loaded into memory at the start of a debug session so that existing breakpoints can automatically be set at that time.
Processing and managing breakpoints
Breakpoints are retained (or persisted) between debug sessions. Because of this, there are some points to be considered regarding how and when breakpoints are set, how to manage breakpoints, and so on.
Breakpoints can be managed (enabled, disabled, removed, and so on.) via the Breakpoints view. Once a breakpoint is created, that breakpoint exists until it is removed. Breakpoints can then automatically be loaded upon session start, but only if its associated load module is first loaded into memory. Otherwise, existing breakpoints are ignored during a debug session unless the associated load module is loaded manually.
To load modules into memory upon session start
To specify the load modules that are loaded into memory upon starting a debug session, the following options exist:
- Load all modules: This default option loads all modules into memory that have associated enabled breakpoints upon session start. A status message detailing whether a module was successfully loaded into memory appears in the Console view. If a module could not be loaded, the breakpoints within that module are skipped.
- Load the main module only: This option only loads the main module into memory at session start. Enabled breakpoints within the main module are set. All other breakpoints are skipped.
- Specify the modules to load: This option provides a checklist of modules that currently have associated enabled breakpoints. All enabled breakpoints within the checked modules are set at session start. All other breakpoints are ignored. Note that the main module is always be loaded into memory regardless of whether it is displayed or checked.
Considerations
Loading modules other than the main module should be done with caution. Please be aware of the following before choosing to load such modules into memory:
- Memory limitations with your program’s address space
- Possible module conflicts between multiple load libraries
- Code Coverage activation of modules that get loaded into your program’s address space
Related Topics
Breakpoints-and-the-Breakpoints-View