CSC 216 F09/Debugging S: Difference between revisions
| Line 12: | Line 12: | ||
===Participants and props=== | ===Participants and props=== | ||
Step by Step Debugging was created in Flash, using 18 frames and screenshots of Eclipse to show where each step over and step into will lead. <br> | |||
Anyone can download the file and go through the exercise on their computer. | |||
The flash file [http://www4.ncsu.edu/~dclong2/debug.swf] | |||
Made by David Long, Dustin Geckler, and Parker Beaman | |||
===The script=== | ===The script=== | ||
Run the flash file. After hitting debug, you are able to choose step over or step into to examine the code further and find the errors. | Run the flash file. After hitting debug, you are able to choose step over or step into to examine the code further and find the errors. | ||
Revision as of 01:54, 17 November 2009
This page is a work in progress
Debugging S
Step by step debugging.
The problem
This exercise is an intro into debugging. It focuses on the step over and step into tools in Eclipse.
Step into enters the next method at the line of code currently being executed. to debug it, while step over executes the next method without entering it in the user interface.
Participants and props
Step by Step Debugging was created in Flash, using 18 frames and screenshots of Eclipse to show where each step over and step into will lead.
Anyone can download the file and go through the exercise on their computer.
The flash file [1]
Made by David Long, Dustin Geckler, and Parker Beaman
The script
Run the flash file. After hitting debug, you are able to choose step over or step into to examine the code further and find the errors.