Enabling, Disabling and Removing Breakpoints

# HG changeset patch # User fturovic # Date 1250018553 18000 # Node ID 393919dade6d76ba045bac9bb4acfe9b14fd7522 # Parent 410577fa5534fc3273379ec88e5159bacca458f2# Parent 2bdd901b072d8eb20d575dd9449ddc6c78df4f05 daily merge diff -r 2bdd901b072d -r 393919dade6d core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm Tue Aug 11 13:27:04 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/bugs_fixed.htm Tue Aug 11 14:22:33 2009 -0500 @@ -15,17 +15,22 @@

Carbide.c++ bugs fixed

This is a comprehensive list of bugs fixed by release:

Bugs Fixed in 2.1.0
2.0.4, 2.0.3, 2.0.2, 2.0.0

Bugs Fixed in 2.2.0
2.1.0, 2.0.4, 2.0.3, 2.0.2, 2.0.0
1.3.1, 1.3.0 , 1.2.2, 1.2.1

Bugs Fixed in v2.2.0

5391 - C++ source hover background color is now customizable. See Window > Preferences > C/C++ > Editor.
9141 - Fixed an issue when setting a breakpoint would force a refresh of the Executables view.

Bugs Fixed in v2.1.0

9164 - Added some diagnostic instrumentation to the Eclipse platform and Carbide to aid users in reporting resource and workspace refreshing issues.
9310 - Can now properly save SBSv2 tools or gcc configurations in the Platform Filtering Preferences panel and added default Apply/Restore controls.
7351 - Fixed an issue where cancelling "Build all configurations" should work and be much faster.

8500 - Fixed an issue that when importing symbols where certain symbols contained erroneous address data.
8500 - Fixed an issue that when importing symbols where certain symbols contained erroneous address data.
8816 - Bash errors should now appear in the Problems view.
8901 - Fixed an issue in the error parser that prevented building Phone Debug builds due to Assembler warnings.
8914 - Corrected an issue with scanning SDKs that cause the scan to repeat endlessly.

Enabling, Disabling and Removing Breakpoints

Use the Toggle Breakpoint command (Ctrl+Shift+B) to set a regular breakpoint in an Editor or Disassembly view. Only a single breakpoint can exist on a source code line. A regular breakpoint suspends program execution when it is hit, or executed, during a debug session. The debugger executes the line of source code that contains the regular breakpoint, then opens the Debug perspective to allow examination and modification.

If a regular breakpoint already exists on the selected line, as indicated by the enabled breakpoint badge () in the marker bar, use Toggle Breakpoint to remove the breakpoint.

Enabling and Disabling breakpoints

Once a source line is selected in an editor or Disassembly view, the methods of toggling breakpoints to be enabled of disabled include:

Choose the Run > Toggle Breakpoint menu option
Right-click and choose Toggle Breakpoint from the context menu
Press Ctrl+Shift+B
Double-click in the marker bar to enable or disable a breakpoint on that source line

Removing breakpoints

In the Breakpoints view, locate the source code line to modify and:

Right-click the breakpoint and choose Remove from the context menu to remove the breakpoint

NOTE Once a breakpoint is removed from the Breakpoints view it cannot be recovered using the Breakpoints view, it must be set in an editor or disassembly view.

Breakpoints must first be loaded and resolved before they can be hit during a debug session. See Resolving Breakpoint States for more information on the various states a breakpoint can exhibit.

See Saving and importing breakpoints for information on storing breakpoint data sets for sharing or re-use.

TIP If you find that a breakpoint is not being hit during a debug session, verify that the EXE or DLL is listed in the Executables view.

TIP If debugging a server launched by a client, you must attach to the server process using the Symbian OS Data view in order to hit the breakpoints in the server. Alternately, you can launch the server and client as two independent EXEs using the same COM port and debug them that way.

Other references

Breakpoints overview

Enabling, Disabling and Removing Breakpoints

If a regular breakpoint already exists on the selected line, as indicated by the enabled breakpoint badge () in the marker bar, use Toggle Breakpoint to remove the breakpoint.

Enabling and Disabling breakpoints

Once a source line is selected in an editor or Disassembly view, the methods of toggling breakpoints to be enabled of disabled include:

Choose the Run > Toggle Breakpoint menu option
Right-click and choose Toggle Breakpoint from the context menu
Press Ctrl+Shift+B
Double-click in the marker bar to enable or disable a breakpoint on that source line

Removing breakpoints

In the Breakpoints view, locate the source code line to modify and:

Right-click the breakpoint and choose Remove from the context menu to remove the breakpoint

NOTE Once a breakpoint is removed from the Breakpoints view it cannot be recovered using the Breakpoints view, it must be set in an editor or disassembly view.

Breakpoints must first be loaded and resolved before they can be hit during a debug session. See Resolving Breakpoint States for more information on the various states a breakpoint can exhibit.

See Saving and importing breakpoints for information on storing breakpoint data sets for sharing or re-use.

TIP If you find that a breakpoint is not being hit during a debug session, verify that the EXE or DLL is listed in the Executables view.

Other references

Breakpoints overview

CDT 6.0 — The final version of CDT included as part of the Galileo release. See the CDT 6.0 News and Noteworthy page for more information.
Java 6.0 — Due to the above changes Carbide has also updated to use the Java 6.0 VM. See Java SE 6 Release Notes page for more information.
Java 6.0 — Due to the above changes Carbide has also updated to use the Java Runtime Environment (JRE) 6.0. See Java SE 6 Release Notes page for more information.

2.1.0

The Symbian OS plug-ins can usually detect when a SDK has been installed, - as described in SDK Support.

SDK Support

To do this: