Breakpoints (Visual Studio)

From RemObjects Software

Jump to: navigation, search

This is a Oxygene Language Feature topic
Feel free to add your notes to this topic below.



Setting Breakpoints

A breakpoint suspends the execution of a program for debugging purposes at the location where it is set.

There are three ways to set a breakpoint:

  • click in the gutter of the appropriate line
  • hit Ctrl-B
  • via the IDE's Debug menu (Debug | New Breakpoint | Break At Function)

The first action is a toggle, i.e. clicking on the breakpoint icon will remove it.

The other two options set a breakpoint for a method and invoke the New Breakpoint dialog:

Image:SetNewBreakpoint.PNG

In the screenshot above, the cursor as in the middle of Main (i.e. where the mouse is positioned).

Breakpoint Icons

Image:BreakpointIcons.PNG

The image above shows the four icons possible:

  • line 50: normal breakpoint
  • line 51: disabled breakpoint
  • line 58: advanced breakpoint
  • line 59: disabled advanced breakpoint


The advanced facilities provide options for the action(s) to take when hit. If stopping is disabled, the shape of the icon changes from a circle to a square (see the screenshots in advanced breakpoints).


Disabling a breakpoint is done via the breakpoint's context menu (right mouse click):

Image:BreakpointMenuDisable.PNG

Clicking on a disabled breakpoint enables it and, of course, a further click removes it.

Using breakpoints

When you run your project via F5 or via the Visual Studio IDE's main menu (Debug | Start), processing will stop at the first breakpoint encountered:

Image:UsingBreakpoints.PNG


For clarity, the Debug toolbar has been undocked. It provides the following facilities (with shortcut key in parentheses):

  • Continue (F5): processing will continue until another break point or to the end of the application if none found
  • Break All (Ctrl+Alt+Break) : in the screenshot above, you will see that this button is currently disabled. It is enabled while the application is actually running and can be used to break the application anywhere, so is most useful for stopping long running (or infinite) loops.
  • Stop Debugging (Shift+F5): runs the rest of the application normally (but see Break All above).
  • Restart (Ctrl+Shift+F5): restart debugging from the beginning of the application.
  • Show Next Statement (Alt+Num): not operational or needed (displays because this is a Visual Studio toolbar).
  • Step Into (F11): if the breakpoint is on a method call, the next stop will be within the called method, otherwise processing will stop at the next line.
  • Step Over (F10): do not step through a call method but process it normally and step to next line in the current method. If the method called contains breakpoint(s), processing will still stop within the method.
  • Step Out (Shift+F11): discontinue stepping through the current method. Processing will continue until the next line of the calling method or the next breakpoint, whichever occurs first.
  • Hex: hexidecimal display is not supported by Chrome (displays because this is a Visual Studio toolbar).
  • Windows (Ctrl+Alt+B): lists the debug windows.


See Also


Product: RemObjects Oxygene (formerly known as Chrome)
Current version: 3.0 Previous Versions: 'Joyride' (2.0), 'Floorshow' (1.5), 'Adrenochrome' (1.0)

Glossary — Keywords — Language Features — Platform Features — Samples — Articles — How To — Issues

Retrieved from "http://wiki.remobjects.com/wiki/Breakpoints_%28Visual_Studio%29"
Personal tools