# HG changeset patch # User fturovic # Date 1250018502 18000 # Node ID 410577fa5534fc3273379ec88e5159bacca458f2 # Parent 5fbe3d7fa2f59c5ac0bcb97d3ea72ccee45b1872 additional broken lins fixed and one image re-added to manual diff -r 5fbe3d7fa2f5 -r 410577fa5534 core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/toggling_breakpoints.htm --- a/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/toggling_breakpoints.htm Tue Aug 11 14:20:41 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/debugger/breakpoints/toggling_breakpoints.htm Tue Aug 11 14:21:42 2009 -0500 @@ -1,38 +1,38 @@ - - - - - - -Enabling, Disabling and Removing Breakpoints - - - -

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:

- -

Removing breakpoints

-

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

- -

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

- - - - + + + + + + +Enabling, Disabling and Removing Breakpoints + + + +

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:

+ +

Removing breakpoints

+

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

+ +

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

+ + + + diff -r 5fbe3d7fa2f5 -r 410577fa5534 core/com.nokia.carbide.cpp.doc.user/html/tasks/AddinganSDK.html --- a/core/com.nokia.carbide.cpp.doc.user/html/tasks/AddinganSDK.html Tue Aug 11 14:20:41 2009 -0500 +++ b/core/com.nokia.carbide.cpp.doc.user/html/tasks/AddinganSDK.html Tue Aug 11 14:21:42 2009 -0500 @@ -9,7 +9,7 @@

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

+ as described in SDK Support.

To do this:

diff -r 5fbe3d7fa2f5 -r 410577fa5534 core/com.nokia.carbide.cpp.doc.user/html/tasks/watchpoints/images/icon_watchpoint_write_resolved.png Binary file core/com.nokia.carbide.cpp.doc.user/html/tasks/watchpoints/images/icon_watchpoint_write_resolved.png has changed