R. Clayton (rclayton@monmouth.edu)
(no date)
I've been testing the exec & fork batch disks and they run for a bit and stop
when I get the following interrupt values:
illegal_instruction_i = 18
invalid_address_i = 19
Are we supposed to be handling these interrupt values in project two or is
something else going with my code?
None of the batch disks should cause an illegal-instruction interrupt; if the
os gets one of those, then the os has probably done something wrong.
The only batch disk that should legitimately throw an invalid-address interrupt
are the pa?-bad.dsk disks. For the moment, the os should just eject the
offending process; for the third assignment the os will have to do more.
If any non-bad batch disk throws an invalid-address interrupt, then the os has
probably done something wrong.
You can run my os on the batch disks to get an idea of the expected behavior.
Make sure you understand the debugging-print command-line options supported by
the simulator and my os; watching my os run without them will not be
very informative.
This archive was generated by hypermail 2.0b3 on Mon Dec 16 2002 - 22:00:05 EST