## Breakpoint Status Indicators

Breakpoints must be located and resolved by the debugger before they can be hit. When a breakpoint is hit in the module, the debugger halts program execution and displays the state of the program in the Debug perspective.

To hit a breakpoint during a debug session, the debugger must first load the symbols for an executable module and then attempt to resolve the breakpoints within the loaded module. Any module listed into the Executables view is available for loading by a debug session. If a module is not present in the Executable view you'll need to import it before the debugger to load and resolve any breakpoints within that module.

You set a breakpoint on any executable line of code that the debugger can resolve. Lines containing comments and other non executable code cannot be assigned a breakpoint as they are normally stripped from the compiled binary. Carbide helps by preventing you from setting a breakpoint on a non-compilable line of code.

When the debugger attempts to resolve a breakpoint the possible results are shown in Table 1.

##### Table 1 Breakpoint—type, icons, and states

Type | Icon | State | Explanation
--- | --- | --- | ---
Enabled |  | Unresolved | The breakpoint is enabled but the symbols for the module are not loaded or the breakpoint was not able to be set within the current function.Breakpoint icon remains in unflagged state indicating unresolved status. If the breakpoint has been set in the source file but not resolved: a debug session has not been launched to resolve the breakpoint. For example, you just set the breakpoint and have yet to launch a debug session. the symbols file containing the breakpoint cannot be found. Ensure the module to debug is present in the Executable view list so the debugger can locate and load the executable for symbol resolution. breakpoint is set on a source line without any executable code breakpoint is located in a deadstripped function not present in the executable
| Resolved | The breakpoint is currently enabled, the symbols for the module are loaded, and the breakpoint located in the executable being debugged. The debugger halts program execution at an enabled breakpoint. resolved — the symbols for the module are loaded and the breakpoint located in the executable that’s currently being debugged, circle icon changes to flagged icon resolved and moved —the breakpoint is not found in the executable at the specified point. Debugger moves breakpoint forward in the current function until a line is found that can be resolved. Breakpoint icon moved to source line matching new breakpoint location and changed to flagged icon
Disabled |  | Unresolved | Indicates that the breakpoint is currently disabled but not located in the executable during a debug session. The debugger does not halt program execution at a disabled breakpoint.
| Resolved | Indicates that the breakpoint is currently disabled and resolved for the source line. The debugger does not halt program execution at a disabled breakpoint.

#### Other references

- Breakpoints overview