You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: app/pages/learn/01_tutorial/01_your-first-java-app/03_writing-java-applications-with-eclipse.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,18 +95,18 @@ When running the program, Eclipse should show the output of the program in the `
95
95
96
96
When a program doesn't do what you expect it to do, you might want to debug it. The process of debugging is explained in [this article](/learn/debugging). Eclipse provides a lot of functionality making it easy to debug Java applications.
97
97
98
-
In order to debug an application, you need to set a breakpoint. When the execution hits that breakpoint, the program will temporarily stop ("suspend"), allow you to inspect its current state and step through the program. To set a breakpoint, you need to double-click on the area to the left of the line you want to stop execution at. After doing that, a blue dot should appear there.
98
+
In order to debug an application, you need to set a breakpoint. When the program gets to executing the line with the breakpoint, it will temporarily stop ("suspend"), allow you to inspect its current state and step through the program. To set a breakpoint, you need to double-click on the area to the left of the line you want to suspend the program at. After doing that, a blue dot should appear there.
99
99
[](/assets/images/eclipse/breakpoint.png)
100
100
101
101
When running a program normally, it will ignore all breakpoints. For debugging, you need to run the program in debug mode. This can be done by clicking on the green button with the bug icon [](/assets/images/eclipse/debug_button.png) next to the run button or using `Debug As` > `Java Application`.
102
102
[](/assets/images/eclipse/debug_button_in_toolbar.png)
103
103
104
-
When the execution hits a breakpoint in debug mode, Eclipse will ask you to switch to the Debug perspective. This perspective gives you more information about the program you are currently debugging so you likely want to do this and click on the `Switch` button.
104
+
When the program execution gets to a breakpoint in debug mode, Eclipse will ask you to switch to the Debug perspective. This perspective gives you more information about the program you are currently debugging so you likely want to do this and click on the `Switch` button.
105
105
[](/assets/images/eclipse/debug_perspective_switch.png)
106
106
107
107
Upon opening the debug perspective, you should still see your code in the middle. However, there should be one line with a green background next to the breakpoint. This indicates the next line the program would execute. On the right side, you should see a `Variables` view containing a list of variables and their current values.
While the program is suspended, you can tell it how to continue executing using buttons in the toolbar at the top.
111
111
[](/assets/images/eclipse/debug_toolbar_buttons.png)
112
-
You can execute one line using `Step Over`[](/assets/images/eclipse/debug_step_over.png) (`F6`), go into a method using `Step Into`[](/assets/images/eclipse/debug_step_into.png) (F5) or continue execution until the next breakpoint with `Resume`[](/assets/images/eclipse/debug_resume.png) (`F8`).
112
+
You can execute one line using `Step Over`[](/assets/images/eclipse/debug_step_over.png) (`F6`), go into a method using `Step Into`[](/assets/images/eclipse/debug_step_into.png) (F5) or continue executing the program until the next breakpoint with `Resume`[](/assets/images/eclipse/debug_resume.png) (`F8`).
0 commit comments