C-Debugging - Debugging in C Haiyan Qiao...

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

View Full Document Right Arrow Icon

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

View Full DocumentRight Arrow Icon

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

View Full DocumentRight Arrow Icon

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

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Debugging in C Haiyan Qiao haiyanq@email.arizona.edu Class plan Enumeration data type (10 minutes) Review: programming errors (5 minutes) Group discussion: your debugging tips (10 minutes) Introduction to debugger GDB (40 minutes) What are the four kinds of errors that may be found in a C program? Syntax errors Run time errors Undetected errors Logical errors Debugging is an integral part of programming. The best cure is prevention Plan your program before you type it Write programs with good style Program in modules Analyze your program before you fix it The better your plan the less likely your program will be to fail and the more likely you'll be to fix it if it does fail. How to debug your program? Plan ahead!!! How did you debug? printf() debugging Use binary search strategies Using debugging tools Debugging with GDB How to start GDB?...
View Full Document

This note was uploaded on 04/03/2008 for the course ECE 175 taught by Professor Grubbs during the Spring '08 term at University of Arizona- Tucson.

Page1 / 15

C-Debugging - Debugging in C Haiyan Qiao...

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

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