FITIn Installation Annotation Running FITIN Fault Injection FITIn Internally Usage
Let us head back to our example. Now, we have to count the number of accesses to state to schedule our first experiment: triggering one false alarm for overload. Under normal ircumstances, each loop-run implies five read operations (lines 18, 21, 25, 30, 32). We select the third iteration and need to flip the least significant bit right before the 14th access. We prepare the run as shown by the first line of Fig. 1. The output also demonstrates the success of the fault injection as we notice one message Elevator overloaded. In a golden run, for example, one can count the number of accesses to monitored variables to spot significant mismatches in the number of expected and observed read accesses. As, under normal conditions, the program runs indefinitely, we have to terminate it by Ctrl-C.
At the end, FITIn prints additional statistics to the output: the overall number of counted variable accesses resulting from load operations from the memory, the accesses to variables that have been annotated by the user until the bit-flip took place, and the overall number of instructions executed, excluding the ones of Valgrind, FITIn, and all function calls the outside of the IR.
