Exercising SDVRP. Initial steps.

Transcription

1 Exercising SDVRP Initial steps. 1. Extract the content of slamsdv.zip 2. Go to the directory slamsdv (extracted in the previous step). 3. Run prepare.cmd 4. Start -> All Programs -> Windows Driver Kits -> WDK > Build Environments -> Windows 7 -> x86 Free Build Environment 5. A console window labeled Windows Win7 x86 Free Build Environment should open. 6. Run in it: > cd sdv_samples Exercise #1. 1. The code of the driver for this exercise is located at C:\WinDDK\ \sdv_samples\fail_drivers\custom1\fai l_driver1\fail_driver1.c. Open it for editing. 2. The specification files (*.slic files) for this exercise are located at C:\WinDDK\SDV\rules\custom1\. You can view them if you need (probably you ll need). 3. In the console window (open in step #5 of the initial steps) 4. The command StaticDV/view of the just run script should have opened GUI with detected errors. Make sure there are 3 detects found:

2 5. Double click on the defect under custommemmove. The specification (CustomMemMove.slic) is correct. There is a bug in the driver code. Try to fix it. Hint: the driver function DriverRead() should ignore the given value of Irp->len : on success it should write into Irp->len. 6. When you fixed the code of the driver, close the GUI window and repeat the steps 3-6 until the defect in custommemmove is resolved (it should change to Passed ): Exercise Keep working in the same console and GUI windows. Look at the defect reports under customlock. Try to fix them. 2. Close the GUI window and in the console window (open in step #5 of the initial steps) 3. If you succeeded to fix the specification violations, you should get the following GUI window:

3 If there are no defects, proceed to Exercise #3. Otherwise (your attempt did not fix the problem) repeat the steps 1-3 until you fix the problem. Exercise 3: 1. Look at the code of the driver (still open after the first step of the first exercise). The line that follows the comment: //DOUBLE_RELEASE_PROBLEM: should have caused a violation of the specification: the lock is released twice in row. 2. Try to correct this inconsistency without commenting out this problematic line. Think where the problem is. 3. Close the GUI window and in the console window (open in step #5 of the initial steps) 4. If you succeeded to correct the inconsistency, you must receive a report about the violation: In this case continue to the step #5. But if you did not receive the defect report, repeat the steps 2-4 until you receive it. 5. Now you are permitted to comment that problematic line out (referred in the step #1). 6. Close the GUI window and in the console window (open in step #5 of the initial steps) 7. If you defined everything right, you should receive no error report:

4 If it is not the situation, uncomment the problematic line and go back to the step #2. 8. On success, attach all the files you changed in the exercises 1-3 to the you ll send to Dima. 9. Close the GUI window and in the console window (open in step #5 of the initial steps) > custom1_clean.cmd 10. Close all the source and specification files you opened until now. Exercise #4 (if time permits). 1. The code of the driver for this exercise is located at C:\WinDDK\ \sdv_samples\fail_drivers\custom3\fai l_driver1\fail_driver1.c. Open it for viewing. 2. The *.slic file for this exercise is located at C:\WinDDK\SDV\rules\custom3\CustomOwnedLock.slic. You can open it if you need (probably you ll need). In the model of this exercise it is allowed to make several locks in row followed by several unlocks in row. What is essential is that: The amount of unlocks should not exceed the amount of locks; When the driver finished processing a request, the lock should be free (unlocked). 3. In the console window (open in step #5 of the initial steps) > custom3_build.cmd 4. The command StaticDV/view of the just run script should have opened GUI with detected errors. Make sure there are 3 detects found:

5 5. Look at the code of the driver. Do you think it violates the specification as listed in the step #2? 6. Upgrade the specification file so that it matched the specification as listed in the step #2. 7. Make sure that after your upgrade, the verification passes. 8. In the console window (open in step #5 of the initial steps) > custom3_clean.cmd 9. On success, attach all the files you changed in this exercise to the you ll send to Dima. Please, send an to with your impressions on the lecture and the user experience. In particular: 1. Were the lecture topics clear? Was it well organized? Is there any particular subject you wish there was more/less focus on? 2. Do you find SDVRP to be useful as a verification tool? 3. Did the user experience help in understanding the use and strength of the tool? 4. Any other comments? 5. Don t forget to attach the files as requested in the step #8 of the exercise #3 and in the step #9 of the exercise #4. 6. Please, answer here the question asked in the step #5 of the exercise #4. Thank you, Dima