Exercise 2: Debugging a 1,000-Iteration Loop — Possible Solution
=================================================================

TASK
Choose the right kind of breakpoint, say why a plain line breakpoint would
be a poor choice, and list the console commands you would use once it stops.

ANSWER
- Kind: a conditional breakpoint, set on the line where the value is
  computed, with a condition that is true only when the value looks wrong
  (for example the running total is negative). The tutorials describe
  conditional breakpoints as stopping only if a condition is true, or after
  a number of hits.
- Why not a plain line breakpoint: it would stop on every one of the 1,000
  iterations, and you would have to press continue until you reached the bad
  one.

ONCE IT STOPS
  p total     inspect a value
  po tasks    print an object's description
  bt          see how execution got here
  n           step over to the next line
  c           continue

CAUTION
The exact way to add a condition (right-click, Edit) comes from tutorials,
not Apple's documentation, so confirm it in your version.