6_Debugging

6_Debugging - Debugging IT DOESNT WORK, NOW WHAT? CMPE13...

Info iconThis preview shows pages 1–5. Sign up to view the full content.

View Full Document Right Arrow Icon
CMPE13 Cyrus Bazeghi I T DOESN T WORK , NOW WHAT ? Debugging
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CMPE13 D EBUGGING WITH H IGH L EVEL L ANGUAGES Same goals as low-level debugging Examine and set values in memory Execute portions of program Stop execution when (and where) desired Want debugging tools to operate on high-level language constructs Examine and set variables, not memory locations Trace and set breakpoints on statements and function calls, not instructions ...but also want access to low-level tools when needed 15-2 2
Background image of page 2
CMPE13 T YPES OF E RRORS Syntactic Errors Input code is not legal Caught by compiler (or other translation mechanism) Semantic Errors Legal code, but not what programmer intended Not caught by compiler, because syntax is correct Algorithmic Errors Problem with the logic of the program Program does what programmer intended, but it doesn't solve the right problem 15-3 3
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
CMPE13 S YNTACTIC E RRORS Common errors: missing semicolon or brace mis-spelled type in declaration
Background image of page 4
Image of page 5
This is the end of the preview. Sign up to access the rest of the document.

This document was uploaded on 08/23/2010.

Page1 / 13

6_Debugging - Debugging IT DOESNT WORK, NOW WHAT? CMPE13...

This preview shows document pages 1 - 5. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online