core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/resolving_breakpoints.htm
equal
deleted
inserted
replaced
8 <link rel="StyleSheet" href="../../../book.css" type="text/css"/> |
8 <link rel="StyleSheet" href="../../../book.css" type="text/css"/> |
9 </head> |
9 </head> |
10 <body > |
10 <body > |
11 <h2> Breakpoint Status Indicators </h2> |
11 <h2> Breakpoint Status Indicators </h2> |
12 <p>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 <a href="../../reference/perspective_debug.htm">Debug</a> perspective. </p> |
12 <p>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 <a href="../../reference/perspective_debug.htm">Debug</a> perspective. </p> |
13 <p>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 <a href="../../reference/view_executables.htm">Executables</a> 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. </p> |
13 <p>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 <a href="../../projects/views/view_executables.htm">Executables</a> 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. </p> |
14 <p>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. </p> |
14 <p>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. </p> |
15 <p>When the debugger attempts to resolve a breakpoint the possible results are shown in Table 1.</p> |
15 <p>When the debugger attempts to resolve a breakpoint the possible results are shown in Table 1.</p> |
16 <h5>Table 1 Breakpoint—type, icons, and states </h5> |
16 <h5>Table 1 Breakpoint—type, icons, and states </h5> |
17 <table width="90%" border="0" cellpadding="2" cellspacing="0"> |
17 <table width="90%" border="0" cellpadding="2" cellspacing="0"> |
18 <tr> |
18 <tr> |