Hints

Remember null is created with
#define NULL 0
In using gdb under the current OS you must use
> list functionname
to view a function. After this is done you can list it in the usual way, set breakpoints and examine variables. The main reason you must do this is two-fold. First you cannot look at OSP internals (-g option not used).
Use gdb and then help to learn about how to use this very useful debugger. You will need to quit with the quit command. You will need to change the compiler in the Makefile to gcc (dbx for cc is having problems). See debug example.
*** To get OSP to use the same seed as I will use in the parameter files (as page 78 of the manual notes) run OSP with
OSP -d parameter-file
This will cause the seed to the random number generator that was used to create my statistics to be used. It will also allow you to check your results with the same seed multiple times (the seed in the parameter file).

For the first programming assignment remember to use the parameter files from the instructor. Remember to check for a NULL PTBR and only dispatch when handling the first interrupt to call the handler.

Critical section programming assignment.

Shell C code for critical section problem.

Critical section quiz.

Test 2 prep questions

Iphone OS notes in pdf.

Notes on debugger (gdb).

First Takehome Quiz

Second Takehome Quiz

Third Takehome Quiz

First programming assignment.

Second programming assignment on CPU scheduling.

Third programming assignment on Memory Management.

On Panopto Survey.

Tutorial slides for the OSP simulator.