Lab Policy and Goals
The goal of these labs is to teach you to use several UNIX tools. You will get the most value out of these labs if you attempt to use the tools to solve the problems at hand - getting good with these tools now will save you many hours in your future software development!
Unless otherwise stated in exercises, the lab code will be automatically copied into your personal gforge project. You should edit it there and check in. The files checked into your directory as of the time that your lab session ends is your submission.
You are free to work either alone or in pairs. If you work in a pair, BOTH names must be listed in the readme.txt file you submit.
Grading
All of the labs together account for 10% of your grade. Grades for each lab will be one of the following:
- zero: no effort or gibberish
- one: not correct, but sensible effort
- two: not correct, but close
- three: correct
- extra: credit correct and elegant
The bonus problems are intentionally difficult, and should prove a challenge to complete within the time limit even to those of you very familiar with the tools.
Calendar
| Week | Date | Activity |
|---|---|---|
| 1 | March 27/28 | Lab 1 (SVN + make - source code control and build systems) |
| 2 | April 3/4 | No Lab - Come in for hacking help! |
| 3 | April 10/11 | Lab 2 (GDB - debugging) |
| 4 | April 17/18 | No Lab - Come in for hacking help! |
| 5 | April 24/25 | Test 1 (Location TBD) |
| 6 | May 1/2 | No Lab - Come in for hacking help! |
| 7 | May 8/9 | Lab 3 (GPROF - profiling) |
| 8 | May 15/16 | No Lab - Come in for hacking help! |
| 9 | May 22/23 | Lab 4 (Debugging concurrent programs) |
| 10 | May 29/30 | No Lab - Come in for hacking help! |