Advertisement
/ 15 []

Debugging Using Eclipse - BusTRAK TeamSoftware Engineering3/23/2005


Debugging. The process of identifying and fixing errors in softwareMainly used to describe run-time errors or incorrect results. Debugging Tips. Prefer compile-time errors to run-time errorsCompiler can spot error quicklyGUI debuggers are much easier to use (Eclipse, Visual Studio) than command-line debuggers (gdb)Fix one error at a time and document each change or use CVS.

Download Presentation

Debugging Using Eclipse

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use only and may not be sold or licensed nor shared on other sites. SlideServe reserves the right to change this policy at anytime.While downloading, If for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.











- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -




Presentation Transcript


Debugging using eclipse l.jpg

Debugging Using Eclipse

BusTRAK Team

Software Engineering

3/23/2005


Debugging l.jpg

Debugging

  • The process of identifying and fixing errors in software

    • Mainly used to describe run-time errors or incorrect results


Debugging tips l.jpg

Debugging Tips

  • Prefer compile-time errors to run-time errors

    • Compiler can spot error quickly

  • GUI debuggers are much easier to use (Eclipse, Visual Studio) than command-line debuggers (gdb)

  • Fix one error at a time and document each change or use CVS


Eclipse debugging l.jpg

Eclipse Debugging

  • Pretty buggy in 3.01 release

  • Clumsy interface

  • But better than using the command-line

  • Everything you need can be found in the Run menu


Eclipse debugging features l.jpg

Eclipse Debugging Features

  • Breakpoints

  • Step into

  • Step over

  • Step return

  • Step Filters

  • Watches

  • Run to line

  • Suspend/Resume/Terminate


Breakpoints l.jpg

Breakpoints

  • Breakpoints cause the thread of execution to suspend and return to the debugger

  • Setting breakpoints in Eclipse is easy, just double-click the left margin


Step into l.jpg

Step Into

  • Executes single (highlighted) statement

  • If statement contains call to method, it steps into the method

  • To use:

    • Must be in Debug Perspective

    • Click from Debug Toolbar or press F5


Step over l.jpg

Step Over

  • Executes single (highlighted) statement

  • If statement contains method call, the entire method is executed without stepping through it

  • To use:

    • Must be in Debug Perspective

    • Click from Debug toolbar or press F6


Step return l.jpg

Step Return

  • All statements in current method are executed

  • Return to where method was called

  • To use:

    • Must be in Debug Perspective

    • Click from Debug toolbar or press F7


Step with filters l.jpg

Step with Filters

  • User can specify which methods Step Filter will execute and return from

  • Usually you would want steps to be made only into methods of your own classes

  • To set filters:

    • Go through Window > Preferences > Java > Debug > Step Filtering


Watches l.jpg

Watches

  • Watches allow you to view (and sometimes change) the value of a variable during execution

  • In Eclipse, watches are set automatically on variables in scope

  • Watches can be found in the Eclipse Debug perspective in the “Variables” window

  • Eclipse allows you to change the value of variables dynamically during runtime


Run to line l.jpg

Run to Line

  • Equivalent to setting a temporary breakpoint


Suspend resume terminate l.jpg

Suspend/Resume/Terminate

  • Suspend pauses the current thread of execution and breaks into the debugger

  • Resume resumes a suspended application

  • Terminate stops the program and debugging process


Slide14 l.jpg

Demo


Questions l.jpg

Questions?