Lab #5: 

Get the various points in this lab checked off by your lab on the week
of 14 October.  It would be good, of course, to have them done the
FIRST week!  Indeed, you will probably want to have done a good deal
of the implementation work prior to coming into lab for checkoffs.

1. In the subdirectory 'problem', you will find a student's bug submission,
   just as we saw it when it came to us via bug-submit (identification
   has been removed, however).  

   a. Try to reproduce the student's problem.  What might have helped
      you to do this more easily?
   
   b. Using gjdb, find out exactly where the program blows up, and why.

   c. Try to find out what the student's program did that eventually caused
      this error to happen.  That is, find out where the offending 
      value that caused the exception was probably inserted.  (Hint, 
      I figured this out almost instantly by judicious use of Ctrl-S 
      in Emacs).

   d. No, you DON'T have to fix the problem! (;->).

2. Look at the file ListHacker.java included in the lab5 directory.  
   There are a number of functions there to fill in.  The challenge is
   to fill them in WITHOUT WRITING ANY LOOPS OR RECURSIVE FUNCTIONS, just
   by calling library functions.  (The library functions probably have 
   loops and recursions in them, but that's OK.) You will find a number
   of import statements at the top of the program that suggest where you
   might look for the answers.