cs 325 home

Assignment 4: Analyze Programming Bugs

Identify and Analyze 3 Bug Cases

This is a non-programming task. Pick 3 bugs. At least one should be a Lisp bug, and ideally at least one should be in another language. Pick real bugs you've encountered. Alternatively, look over postings to comp.lang.lisp, comp.lang.javascript, comp.lang.java.help and so on. These are all available at Google Groups. Don't make up some bugs, or retrieve a dim memory of a bug.

Do not use the "list not updated" class of bugs discussed here and in class.

For each bug, write an informal description with the following structure (plus any other items you think relevant):

Submit Report

Email the above in PLAIN TEXT format (no attachments, no HTML or Rich Text) to c25@cs.northwestern.edu

There's 4 possible grades for this assignment: nothing, substandard, OK, excellent. I'm expecting most to be OK. Substandard means you didn't do what was asked for or didn't think very hard. Excellent means if someone asked me about you, I'd say "they did a really nice analysis of programming bugs."

Cautionary Notes

A bug is not a simple mistake with an easy fix, e.g., the symptom is the error message "NIL is not a number" and the cause is that you forgot to initialize a variable to 0. No one posts a bug like that because they don't need to. They can figure it out themselves.

Remember the Boggle® Factor: in the Boggle hidden word game, a word doesn't count if someone else finds it. Similarly, in this exercise, your assignment is weaker if it duplicates other work.

Comments? Send mail to Chris Riesbeck.