Quick update to add details on xv6 tests
This commit is contained in:
committed by
GitHub
parent
935e792457
commit
57e8798ce5
@@ -59,6 +59,31 @@ Using gdb (the debugger) may be helpful in understanding code, doing code
|
|||||||
traces, and is helpful for later projects too. Get familiar with this fine
|
traces, and is helpful for later projects too. Get familiar with this fine
|
||||||
tool!
|
tool!
|
||||||
|
|
||||||
|
# Running Tests
|
||||||
|
|
||||||
|
Running tests for your system call is easy. Just do the following from
|
||||||
|
inside the `initial-xv6` directory:
|
||||||
|
|
||||||
|
```sh
|
||||||
|
prompt> ./test-getreadcounts.sh
|
||||||
|
```
|
||||||
|
|
||||||
|
If you implemented things correctly, you should get some notification
|
||||||
|
that the tests passed. If not ...
|
||||||
|
|
||||||
|
The tests assume that xv6 source code is found in the `src/` subdirectory.
|
||||||
|
If it's not there, the script will complain.
|
||||||
|
|
||||||
|
The test script does a one-time clean build of your xv6 source code
|
||||||
|
using a newly generated makefile called `Makefile.test`. You can use
|
||||||
|
this when debugging (assuming you ever make mistakes, that is), e.g.:
|
||||||
|
|
||||||
|
```sh
|
||||||
|
prompt> make -f Makefile.test qemu-nox
|
||||||
|
```
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user