Debugging in CMSC 131 Fall 2008: Using the Eclipse Debugger - Prof. Jandelyn Dawn Plane, Study notes of Computer Science

Download Debugging in CMSC 131 Fall 2008: Using the Eclipse Debugger - Prof. Jandelyn Dawn Plane and more Study notes Computer Science in PDF only on Docsity! 1 CMSC 131 Fall 2008 Jan Plane Lecture Set #10: Debugging 1. Complete Class Example 2. The Eclipse Debugger CMSC 131 Fall 2008 Jan Plane 1 Complete Example – Putting the pieces together
Constructors
default constructor
constructors with parameters
copy constructors
Data
data members: instance/static and public/private
local variables
stack and heap
null references
Methods
instance/static and public/private
overloading: toString and others
Libraries
importing and using methods from the library (the API)
JUnit Testing
Exceptions
Throwing, trying, catching 2 CMSC 131 Fall 2008 Jan Plane 2 The problem
Problem
JUnit can only tell if that passes or fails and where
Need a way to be able to see what is in memory (variables) at every step to be able to do complete trace [like that call stack examples we have been doing]
Solution
The debugger gives the ability to go through the code – displaying additional information similar to the by-hand call stack that we have been doing CMSC 131 Fall 2008 Jan Plane 3 Terminology
Break Point
drop a marker into the code so when it runs the execution will stop at that point
allows you to not have to go step by step through things you believe are correct
Step Over
takes one step in the current method
if that step is a method call, it performs that whole method call and steps to the next line in the current method
Step Into
takes one step in the current method
if that step is a method call, it steps into that method so that you can then step through it before getting to the next line in the method you were in