Libraries and Debugging

Slides:



Advertisements
Similar presentations
COMPUTER PROGRAMMING I Essential Standard 5.02 Understand Breakpoint, Watch Window, and Try And Catch to Find Errors.
Advertisements

Annoucements  Next labs 9 and 10 are paired for everyone. So don’t miss the lab.  There is a review session for the quiz on Monday, November 4, at 8:00.
Debugging Mohammad Zikky, M.T. 2 Debugging Introduction (1 of 2)  Debugging is methodical process for removing mistakes in a program  So important,
IMGD 1001: Debugging. 2 Debugging Introduction (1 of 2)  Debugging is methodical process for removing mistakes in a program  So important, whole set.
Interactive Media and Game Development Debugging.
Chapter 3.5 Debugging Games
Interactive Media and Game Development Debugging.
Debugging Introduction to Computing Science and Programming I.
IMGD 1001: Debugging by Mark Claypool Robert W. Lindeman
Interactive Media and Game Development Debugging.
Debugging CPSC 315 – Programming Studio Fall 2008.
The IDE (Integrated Development Environment) provides a DEBUGGER for locating and correcting errors in program logic (logic errors not syntax errors) The.
XP 1 Working with JavaScript Creating a Programmable Web Page for North Pole Novelties Tutorial 10.
How to Debug VB .NET Code.
Interactive Media and Game Development Debugging.
2/9/2007EECS150 Lab Lecture #41 Debugging EECS150 Spring2007 – Lab Lecture #4 Laura Pelton Greg Gibeling.
02/10/06EECS150 Lab Lecture #41 Debugging EECS150 Spring 2006 – Lab Lecture #4 Philip Godoy Greg Gibeling.
Using a Debugger. SWC What is ”debugging”? An error in a computer program is often called a ”bug”… …so, to ”debug” is to find and get rid of errors in.
Jun 16, 2014IAT 2651 Debugging. Dialectical Materialism  Dialectical materialism is a strand of Marxism, synthesizing Hegel's dialectics, which proposes.
Testing and Debugging Version 1.0. All kinds of things can go wrong when you are developing a program. The compiler discovers syntax errors in your code.
Testing. 2 Overview Testing and debugging are important activities in software development. Techniques and tools are introduced. Material borrowed here.
Testing and Debugging Session 9 LBSC 790 / INFM 718B Building the Human-Computer Interface.
1 Κατανεμημένες Διαδικτυακές Εφαρμογές Πολυμέσων Γιάννης Πετράκης.
Making Good Code AKA: So, You Wrote Some Code. Now What? Ray Haggerty July 23, 2015.
BMTRY 789 Lecture 11: Debugging Readings – Chapter 10 (3 rd Ed) from “The Little SAS Book” Lab Problems – None Homework Due – None Final Project Presentations.
1 Debugging and Syntax Errors in C++. 2 Debugging – a process of finding and fixing bugs (errors or mistakes) in a computer program.
Debugging tools in Flash CIS 126. Debugging Flash provides several tools for testing ActionScript in your SWF files. –The Debugger, lets you find errors.
Debugging What coders (programmers) do to find the errors (“bugs”) in their own programs “Bugs” – Admiral Grace Hopper, developer of the world’s first.
JavaScript Introduction and Background. 2 Web languages Three formal languages HTML JavaScript CSS Three different tasks Document description Client-side.
AVCE ICT – Unit 7 - Programming Session 12 - Debugging.
Error Analysis Logic Errors.
FOP: Multi-Screen Apps
Development Environment
Winter 2009 Tutorial #6 Arrays Part 2, Structures, Debugger
14 Compilers, Interpreters and Debuggers
User-Written Functions
CSE 374 Programming Concepts & Tools
Eclipse Navigation & Usage.
Testing and Debugging.
Computer Programming I
LESSON 20.
Chapter 5 Conclusion CIS 61.
CSS 161: Fundamentals of Computing
Using Visual Studio with C#
CSE341: Programming Languages Section 1
Chapter 15 Debugging.
CSCE 315 – Programming Studio, Fall 2017 Tanzir Ahmed
CSE341: Programming Languages Section 1
Programming Fundamentals (750113) Ch1. Problem Solving
Lesson 12.
Tonga Institute of Higher Education
We’re moving on to more recap from other programming languages
Debugging at Scale.
Debugging Taken from notes by Dr. Neil Moore
Chapter 15 Debugging.
Error Analysis Runtime Errors.
EECS150 Fall 2007 – Lab Lecture #4 Shah Bawany
Debugging EECS150 Fall Lab Lecture #4 Sarah Swisher
Programming Fundamentals (750113) Ch1. Problem Solving
Debugging Taken from notes by Dr. Neil Moore
Debugging EECS150 Fall Lab Lecture #4 Sarah Swisher
IDE’s and Debugging.
Programming Fundamentals (750113) Ch1. Problem Solving
An Introduction to Debugging
CISC101 Reminders Assignment 3 due next Friday. Winter 2019
Chapter 3 Debugging Section 3.4
Chapter 15 Debugging.
CHAPTER 6 Testing and Debugging.
Chapter 15 Debugging.
Presentation transcript:

Libraries and Debugging

Introduction Debugging is methodical process for removing mistakes in program So important, whole set of tools to help. Called “debuggers” Trace code, print values, profile New Integrated Development Environments (IDEs) (such as Game Maker) have it built in But debugging still frustrating Beginners not know how to proceed Even advanced can get “stuck” Don’t know how long takes to find Variance can be high What are some tips? What method can be applied?

Outline 5-step debugging process Prevention Game Maker specifics Debugging tips

Step 1: Reproduce the Problem Consistently Find case where always occurs “Sometimes game crashes after kill boss” doesn’t help much Identify steps to get to bug Ex: start single player, room 2, jump to top platform, attack left, … Produce systematic way to reproduce

Step 2: Collect Clues Collect clues as to bug Clues suggest where problem might be Ex: if crash using projectile, what about that code that handles projectile creation and shooting? And beware that some clues are false Ex: if bug follows explosion may think they are related, but may be from something else Don’t spend too long - get in and observe Ex: see reference pointer from arrow to unit that shot arrow should get experience points, but it is NULL That’s the bug, but why is it NULL?

Step 3: Pinpoint Error 1) Propose a hypothesis and prove or disprove Ex: suppose arrow pointer corrupted during flight. Add code to print out values of arrow in air. But equals same value that crashes. Hypothesis is wrong. But now have new clue. Ex: suppose unit deleted before experience points added. Print out values of all in camp before fire and all deleted. Yep, that’s it. Or, 2) divide-and-conquer method (note, can use with hypothesis test above, too) Sherlock Holmes: “when you have eliminated the impossible, whatever remains, however improbably, must be the truth” Setting breakpoints, look at all values, until discover bug The “divide” part means break it into smaller sections Ex: if crash, put breakpoint ½ way. Is it before or after? Repeat. Look for anomalies, NULL or NAN values

Step 4: Repair the Problem Propose solution. Exact solution depends upon stage of problem. Ex: late in code cannot change data structures. Too many other parts use. Worry about “ripple” effects. Ideally, want original coder to fix If not possible, at least try to talk with original coder for insights. Consider other similar cases, even if not yet reported Ex: other projectiles may cause same problem as arrows did

Step 5: Test Solution Obvious, but can be overlooked if programmer is sure they have fix (but programmer can be wrong!) So, test that solution repairs bug Best by independent tester Test if other bugs introduced (beware “ripple” effect)

Outline 5-step debugging process (done) Prevention (next) Game Maker specifics Debugging tips

Debugging Prevention Add infrastructure, tools to assist Alter game variables on fly (speed up debugging) Visual diagnostics (maybe on avatars) Log data (events, units, code, time stamps) Indent code, use comments (in Game Maker) Use consistent style, variable names Ex: spr_boss, obj_boss Avoid duplicating code – hard to fix if bug Use a script Avoid hard-coded values – makes brittle Always initialize variables when declared Verify coverage (test all code) when testing

Outline 5-step debugging process (done) Prevention (done) Game Maker specifics (next) Debugging tips

Game Maker – Print Messages Display a Message object  main2  info Or, in code (control  code) show_message(“Executed this code“) show_message(“num:“ + string(num_here)) Beware if done every step! Save code ahead of time Use task manager to kill Ctrl-Alt-Delete  Task Manager Process is name of game file, not GameMaker.exe

Game Maker – Debug Mode Ex: easy obj_hero.y obj_hero.can_shoot Save/load Look at instances, global variables, local variables Execute code Set speed

Game Maker – Print Debug Messages Like show_message() but in debug mode only Note, doesn’t pause In code show_debug_message(“Executed this code“) Need to run in debug mode Debug information  Tools  Show messages

Game Maker – Log Messages Write messages to file Example: At beginning (maybe create log object) global.log_name = “logfile“; global.fid = file_text_open_write(global.log_name); Then, where needed: file_text_write_string(global.fid,”Debug message here”) ; Close when done (object  event other  game end): file_text_close(global.fid) More file operations (look online) possible Note: files also useful for save/load game, etc.  

Game Maker – Script/Code Syntax

Game Maker – Error Messages (1 of 2) Pay attention! Refers to: Object Event Line number Variable name Help pinpoint problem Refer to object and method and offending code

Game Maker – Error Messages (2 of 2) Can write messages to log file Can ignore messages Use “error_last” and “error_occurred” for custom handling Typically, use only in release

Debugging Tips (1 of 3) One thing at a time Fix one thing at a time – don’t try to fix multiple problems Change one thing at a time – test hypothesis. Change back if doesn’t fix problem. Start with simpler case that works - then add more complex code, one thing at a time Question your assumptions – don’t even assume simple stuff works, or “mature” products Ex: libraries and tutorials can have bugs

Debugging Tips (2 of 3) Check code recently changed – if bug appears, may be in latest code (not even yours!) Use debugger – breakpoints, memory watches, stack … Break complex calculations into steps – may be equation that is at fault or “cast” badly Check boundary conditions – classic “off by one” for loops, etc. Minimize randomness – Ex: can be caused by random seed or player input. Fix input (script player) so reproducible

Debugging Tips (3 of 3) Take a break – too close, can’t see it. Remove to provide fresh prospective Explain bug to someone else – helps retrace steps, and others provide alternate hypotheses Debug with partner – provides new techniques Same advantage with code reviews, peer programming Get outside help – tech support for consoles, Web examples, libraries, …