3.1. Setting Breakpoints
To set breakpoints right click in the small left column in your source code editor and select toggle breakpoint. Or you can double click on this place.
You can debug your application with selecting your Java file which contains a main method, right click it and select Run -> Debug.
Tip
If you have not defined any breakpoints this will run your program as normal. To debug the program you need to define breakpoints.If you start the debugger the first time Eclipse will asked you if you want to switch to the debug perspective. Answer "yes", you should then see a perspective similar to the following.
You can use F5 / F6, F7 and F8 to step through your coding.
Table 1. Debugging Key bindings
| Command | Description |
|---|---|
| F5 | Goes to the next step in your program. If the next step is a method / function this command will jump into the associated code. |
| F6 | F6 will step over the call, e.g. it will call a method / function without entering the associated code. |
| F7 | F7 will go to the caller of the method/ function. So this will leave the current code and go to the calling code. |
| F8 | Use F8 to go to the next breakpoint. If no further breakpoint is encountered then the program will normally run. |
You can of course use the ui to debug. The following displays the keybindings for the debug buttons.
The view "Variables" displays fields and local variables from the current stack.
Use the menu to display static variables.
Via the menu you can also customize the displayed columns, e.g. you can show the acutual and the declared type.
Another nice feature is the the "New Detail Formater" in which you can define how a variable is displayed. For example the toString method in our counter shows something meaningless, e.g. "de.vogella.debug.first.Counter@587c94". Use right mouse click on the variable -> "New Details Formater"
Maintain the following code to get the output "0" (or whatever is field result holds at this point).
0 comments:
Post a Comment