X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=doc%2Fuserprog.texi;h=78ef78d8bfc8d9ba3e41a5b67407f7a1390e01e7;hb=c37b82251bbe85edf2d46284f6d4b43b92b09182;hp=0746b2e68f791af7545793a3458bd5d6ed4851a3;hpb=494fd8674048f3d8e8b9203b090448768ac45c27;p=pintos-anon

diff --git a/doc/userprog.texi b/doc/userprog.texi
index 0746b2e..78ef78d 100644
--- a/doc/userprog.texi
+++ b/doc/userprog.texi
@@ -474,8 +474,11 @@ turn invokes the system call interrupt and returns.
 
 When you're done with this part, and forevermore, Pintos should be
 bulletproof.  Nothing that a user program can do should ever cause the
-OS to crash, halt, assert fail, or otherwise stop running.  The sole
-exception is a call to the @code{halt} system call.
+OS to crash, halt, assert fail, or otherwise stop running.  It is
+important to emphasize this point: our tests will try to break your
+system calls in many, many ways.  You need to think of all the corner
+cases and handle them.  The sole way a user program should be able to
+cause the OS to halt is by invoking the @code{halt} system call.
 
 If a system call is passed an invalid argument, acceptable options
 include returning an error value (for those calls that return a