Breakpoints

# HG changeset patch # User fturovic # Date 1278703047 18000 # Node ID c8b627039298e5c85d2a81b30cf8f9cbe0abaae3 # Parent 58e49b4c270c6289ca4590ff919a2a0009a3d681 revised variables, watchpoints pages with new images, fixed broken links in F1 help too diff -r 58e49b4c270c -r c8b627039298 core/com.nokia.carbide.cpp.doc.user/html/concepts/breakpoints.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/breakpoints.htm Fri Jul 09 09:44:18 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/breakpoints.htm Fri Jul 09 14:17:27 2010 -0500 @@ -1,66 +1,66 @@ - - - - - - -Breakpoints - - - -

Breakpoints

A breakpoint is a marker set on a specific line of source code and is designed to halt program execution when encountered by the debugger. After you set a breakpoint at a key point in the program, you can halt its execution, examine its current state, and check register and variable values. You can also change values and alter the flow of normal program execution. Setting breakpoints helps you debug your program and verify its efficiency.

A project can have multiple breakpoints set in the source code files. All breakpoints in a project are shown in the Breakpoints view. Breakpoints are enabled or disabled on the currently selected line within a source code editor by selecting the Run > Toggle Breakpoint menu option, right-clicking the marker bar in the editor and selecting Toggle Breakpoint, or by pressing CTRL-SHIFT-B.

You can 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. The debugger must load the symbols for a module before it can attempt to resolve breakpoints within the module. This is most easily done using the Executables view to import a binary file, especially if the binary is not in the workspace.

When the debugger attempts to resolve a breakpoint it will result in:

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.
unresolved — if the symbols for the module are not loaded or the breakpoint was not able to be set within the current function. This may indicate no executable code in the source line or a deadstripped function not present in the executable. Breakpoint icon remains in unflagged state indicating unresolved status.

Breakpoints have enabled and disabled types as well as resolved and unresolved states. Table 1 explains the different breakpoint types and states.

Table 1 Breakpoint—type and states

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Type	State	Explanation
Enabled	Unresolved	Indicates that the breakpoint is currently enabled but not located in the executable during a debug session. Debugger cannot halt program execution.
Enabled	Resolved	Indicates that the breakpoint is currently enabled and resolved for the source line. The debugger halts program execution at an enabled breakpoint.
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.
Disabled	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 + + + +

Breakpoints Overview

When the debugger attempts to resolve a breakpoint it will result in:

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.
unresolved — if the symbols for the module are not loaded or the breakpoint was not able to be set within the current function. This may indicate no executable code in the source line or a deadstripped function not present in the executable. Breakpoint icon remains in unflagged state indicating unresolved status.

Breakpoints have enabled and disabled types as well as resolved and unresolved states. Table 1 explains the different breakpoint types and states.

Table 1 Breakpoint—type and states

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Type	State	Explanation
Enabled	Unresolved	Indicates that the breakpoint is currently enabled but not located in the executable during a debug session. Debugger cannot halt program execution.
Enabled	Resolved	Indicates that the breakpoint is currently enabled and resolved for the source line. The debugger halts program execution at an enabled breakpoint.
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.
Disabled	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

+ + + + diff -r 58e49b4c270c -r c8b627039298 core/com.nokia.carbide.cpp.doc.user/html/context_help/eclipse_dialogs_help.xml --- a/core/com.nokia.carbide.cpp.doc.user/html/context_help/eclipse_dialogs_help.xml Fri Jul 09 09:44:18 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/context_help/eclipse_dialogs_help.xml Fri Jul 09 14:17:27 2010 -0500 @@ -20,8 +20,12 @@ The Debug view shows the target debugging information in a tree hierarchy. - - + + + + + + @@ -29,9 +33,8 @@ Use the Variables view to manipulate the variables or variable hierarchy used in source code. - - - + + @@ -39,8 +42,10 @@ Use the Breakpoints view to examine, enable or disable the breakpoints in one or more build configurations. - - + + + + @@ -48,10 +53,18 @@ Use the Expressions view to monitor and manipulate variables, structures, and arrays. - - - - + + + + + + + + + + Find elements in view. + + @@ -280,6 +293,7 @@ + Symbian OS Select the project, class, or file to create. @@ -290,11 +304,10 @@ + Importing projects for development or debugging. Select the type of file to import for debugging. - - @@ -306,8 +319,8 @@ - Use the Console view to show the output of a process and provide keyboard input to a process. - + Exporting from Carbide.c++ + diff -r 58e49b4c270c -r c8b627039298 core/com.nokia.carbide.cpp.doc.user/html/debugger/images/icon_add.png Binary file core/com.nokia.carbide.cpp.doc.user/html/debugger/images/icon_add.png has changed diff -r 58e49b4c270c -r c8b627039298 core/com.nokia.carbide.cpp.doc.user/html/debugger/images/menu_vew_expressions_01.png Binary file core/com.nokia.carbide.cpp.doc.user/html/debugger/images/menu_vew_expressions_01.png has changed diff -r 58e49b4c270c -r c8b627039298 core/com.nokia.carbide.cpp.doc.user/html/debugger/images/menu_vew_expressions_02.png Binary file core/com.nokia.carbide.cpp.doc.user/html/debugger/images/menu_vew_expressions_02.png has changed diff -r 58e49b4c270c -r c8b627039298 core/com.nokia.carbide.cpp.doc.user/html/debugger/images/view_expressions.png Binary file core/com.nokia.carbide.cpp.doc.user/html/debugger/images/view_expressions.png has changed diff -r 58e49b4c270c -r c8b627039298 core/com.nokia.carbide.cpp.doc.user/html/debugger/images/wnd_add_watch_expr.png Binary file core/com.nokia.carbide.cpp.doc.user/html/debugger/images/wnd_add_watch_expr.png has changed diff -r 58e49b4c270c -r c8b627039298 core/com.nokia.carbide.cpp.doc.user/html/debugger/images/wnd_find_expressions.png Binary file core/com.nokia.carbide.cpp.doc.user/html/debugger/images/wnd_find_expressions.png has changed diff -r 58e49b4c270c -r c8b627039298 core/com.nokia.carbide.cpp.doc.user/html/debugger/variables/viewing_expressions.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/variables/viewing_expressions.htm Fri Jul 09 09:44:18 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/variables/viewing_expressions.htm Fri Jul 09 14:17:27 2010 -0500 @@ -20,20 +20,20 @@

Expressions list pane—Lists expressions and expression hierarchies. Click the hierarchical controls to expand or collapse the expression. Right-click to open the Expressions view context menu.

Value pane—Shows the current value of each corresponding expression. Double-click a value to change it. Right-click to set viewing options.

Figure 1 - Expressions view

Expressions view toolbar icons

The following commands appear on the Expressions view toolbar:

- - - + + + - + @@ -46,6 +46,12 @@ + + + + + @@ -55,10 +61,16 @@ + + + + +

Item	Icons	Explanation	Item	Icons
Show Type Names		Toggles the display of type names in the Expressions view.	Toggles the display of type names in the Expressions view.
Show Logical Structure	Collapses all expanded expressions into the top level.
Create a New Watch Expression		Click to open the Add New Expression dialog. Enter the expression to add, then click OK. +
Remove Selected Expression		Click to remove all currently selected expressions from the expressions list.		Click to remove all expressions from the expressions list.
View Menu		Click the View Menu icon to set the layout of the Expressions view. +

Expressions view context menu options

Right-click in the Expression's pane in the Expressions view to access the context menu commands shown in Figure 2.

Expressions view context menu

Figure 2. Expressions view context menu commands (Expression list pane)

The commands include:

@@ -68,33 +80,35 @@ - + - + - + - + - + +

- + @@ -109,8 +123,32 @@ - - + + + + + + + + + + + + + + + + + +

Select All	Selects all the expressions shown in the Expressions view.	Selects all the expressions shown in the Expressions view.
Copy Expressions	Copies the selected expressions to the clipboard.	Copies the selected expressions to the clipboard. + NOTE Only the selected expressions visible in the Expressions view are copied. Expressions listed outside the boundary of the view are not in memory and can't be copied at this time.
Remove	Remove the selected expressions from the Expressions view list.	Remove the selected expressions from the Expressions view list. +
Remove All	Remove all expressions from the Expressions view list.	Remove all expressions from the Expressions view list.
Find...	Opens a Find dialog to search the Expressions view list.	Opens a Find dialog to search the Expressions view list. Enter the expression to search for and click OK. +
Change Value...	Opens the Set Value dialog where you can modify the value assigned to the selected expressions. Change the value and click OK. -
Add Watch Expression...	Opens the Add Watch Exression dialog for creation of a new expression. -	Opens the Add Watch Exression dialog for creation of a new expression.
Disable	Opens the Edit Watch Expression dialog where you can modify the expression and enable it for automatic evaluation.
Reevaluate Watch Expression	Forces the expression to be reevaluated. Useful after the expressions has been edited or not evaluated due to being disabled.	Add Watchpoint (C/C++)...	Opens the Add Watchpoint dialog enabling you to define a watchpoint on the variable. +
Cast To Type...	Opens the Cast to Type dialog where you can assign a new type to the expression. Enter the type and click OK. + All cast expressions are then shown using the Restore Original Type menu option making them easy to identify and restore later.
Display As Array...	Opens the Display as Array dialog where you can set array parameters to show the variables. Enter the Start index and Length, then click OK to update how the variables are shown in the Variables view.
Format	Change the selected variable's display format. The default setting is Natural, or the format assigned when the variable is defined. For example, the decimal value of 256 would appear as: + + Binary (0b100000) + Natural (256) + Decimal (256) + Hexadecimal (0x100) +
Watch	Creates a watchpoint on the selected variable and displays it in the Watchpoint view.

Other references

diff -r 58e49b4c270c -r c8b627039298 core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/status_watchpoints.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/status_watchpoints.htm Fri Jul 09 09:44:18 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/status_watchpoints.htm Fri Jul 09 14:17:27 2010 -0500 @@ -14,7 +14,7 @@

An enabled watchpoint has a non-gray icon () indicating that program execution halts when encountered.
A disabled watchpoint displays a gray icon () indicating that program execution will not stop when encountered.
A resolved watchpoint has a small checkmark badge ( ) indicating that the debugger has located it in memory during program launch. When resolved, the debugger can halt program execution if the watchpoint is encountered.
A resolved watchpoint has a small checkmark badge () indicating that the debugger has located it in memory during program launch. When resolved, the debugger can halt program execution if the watchpoint is encountered.

In effect, a watchpoint that is enabled by the user and resolved by the debugger during program launch can halt program execution. The table below shows the various states that cause the debugger to halt program execution:

Table 1 Watchpoint—stop execution chart

diff -r 58e49b4c270c -r c8b627039298 core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/watchpoints.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/watchpoints.htm Fri Jul 09 09:44:18 2010 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/watchpoints/watchpoints.htm Fri Jul 09 14:17:27 2010 -0500 @@ -5,16 +5,16 @@ Watchpoints Overview - +

Watchpoints Overview

Use watchpoints (sometimes referred to as access breakpoints) to halt program execution when a specific global location is accessed. After you set a watchpoint at a key point in memory, you can halt program execution whenever that point in memory is written to or read from. You can then examine the call chain, check register and variable values, and step through your code. You can also change values and alter the flow of normal program execution.

A watchpoint must be both enabled and resolved during a debug session in order to halt program execution. The Breakpoints view indicates the status of any watchpoint using a set of common icons and checkmark status badge. These include:

An enabled watchpoint has a non-gray icon () indicating that program execution halts when encountered.
A disabled watchpoint displays a gray icon () indicating that program execution will not stop when encountered.
A resolved watchpoint has a small checkmark badge ( ) indicating that the debugger has located it in memory during program launch. When resolved, the debugger can halt program execution if the watchpoint is encountered.
An enabled watchpoint has a non-gray icon () indicating that program execution halts when encountered.
A disabled watchpoint displays a gray icon () indicating that program execution will not stop when encountered.
A resolved watchpoint has a small checkmark badge () indicating that the debugger has located it in memory during program launch. When resolved, the debugger can halt program execution if the watchpoint is encountered.

Table 1 Watchpoint—stop execution chart

@@ -57,39 +57,39 @@ Write enabled -

The watchpoint is activated for write access operations on the specific memory location and if resolved, will halt program execution on a write operation at the watchpoint.

disabled -

Watchpoint is disabled for the source line, debugger does not halt program execution on a write operation.

Read enabled -

The watchpoint is activated for read access operations on the specific memory location and if resolved, will halt program execution on a read operation at the watchpoint.

disabled -

Watchpoint is disabled for the source line, debugger does not halt program execution on a read operation.

Write/Read enabled -

The watchpoint is activated for both read and write access operations on the specific memory location and if resolved, will halt program execution on any read or write operation at the watchpoint.

disabled -

Watchpoint is disabled for the source line, debugger does not halt program execution on a read or write operation.