get_sign.rs done

examples/get_sign.rs

@@ -108,14 +108,14 @@ mod ll {
 //
 // What was the generated hash.
 //
-// [your answer here]
+// [get_sign-85c57be6132dac1d.ll]
 //
 // B) Inspecting the test cases.
 //
 // Figure out to run `ktest-tool` on the generated test cases.
 // (Hint, it is just a matter of paths.)
 //
-// [your answer here]
+// [ ktest-tool examples/klee-out-0/test000001.ktest]
 //
 // C) Replaying your test cases.
 //
@@ -135,7 +135,7 @@ mod ll {
 //
 // > ls *.o
 //
-// [your answer here]
+// [get_sign-85c57be6132dac1d.o]
 //
 // Now we need to link it with the `libkleeRuntest`.
 //
@@ -153,15 +153,15 @@ mod ll {
 //
 // Now run the code in the debugger. What path was triggered.
 //
-// [your answer here]
+// [return -1;]
 //
 // Change to test000002, what path does it trigger.
 //
-// [your answer here]
+// [return 1;]
 //
 // And finally change to test000003, what path was triggered.
 //
-// [your answer here]
+// [return 0;]
 //
 // D) Remarks and conclusions.
 //