Eclipse Debugging - I
16 June 2008Following are Eclipse debugging features: Breakpoints, Step into, Step over, Step return, Step Filters, Watches, Run to line, Suspend/Resume/Terminate. You should know each of these for debugging your Java programs. I will try to introduce these in the next few posts.
We use breakpoints in our Java source to cause the thread of execution to suspend and return to the debugger. To set breakpoints in Eclipse, simply double-click the left margin.
Use ‘Step Into’, to execute single highlighted statement. If a statement contains call to method, then ‘Step Into’ steps into the method. In the debug perspective, F5 is used for ‘Step Into’.
‘Step Over’ also executes single highlighted statement but the difference is that if the statement contains method call, then the method is executed without stepping in to it. Use it if you do not want to go into a method while debugging. In the debug perspective, F6 is used for ‘Step Over.
Related Posts:
- Debugging Remote Java Application - I
- Eclipse Debugging - III
- Eclipse Debugging - II
- Debugging Remote Java Application - II
- Enabling Debugging - domain.xml
- Enabling Debugging - Administration Console
- Debugging In Eclipse IDE
- An Introduction To JUnit
- Enabling Debugging - asadmin
- Creating J2ME MIDlet Project - I
Top Of Page | Trackback
If you found this page useful, consider linking to it. Simply copy and paste the code below into your web site.
It will look like this: Eclipse Debugging - I
