christoph/experimental-evaluation-of-webassembly-under-transient-fault-conditions-for-safety-critical-systems
1
Fork 0
Code Activity

Add golden run and pilot to glossary

Browse Source
This commit is contained in:
christoph
2026-09-10 20:04:36 +02:00
parent e9078ee17f
commit 7893267198
2 changed files with 12 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
chapters/03_background/03_03_fail.tex
+2 -2
View File
@@ -20,8 +20,8 @@ To perform a vulnerability analysis, the examined program needs to be instrument
\begin{codeblock}[label=lst:tracefencemarkers]{Trace Region Fence}{.cpp}
\inputminted{cpp}{\subfix{listings/tracefence.cpp}}
\end{codeblock}
\Gls{fail} then records the instruction pointer changes and memory accesses inside this region during the so-called \textquote{golden run}: a faultless execution of the program that determines which injections should be performed during the campaign.
Then, the golden run is enriched with the traced region's disassembly to take into account the register reads and writes.
\Gls{fail} then records the instruction pointer changes and memory accesses inside this region during the so-called \gls{goldenrun}: a faultless execution of the program that determines which injections should be performed during the campaign.
Then, the \gls{goldenrun} is enriched with the traced region's disassembly to take into account the register reads and writes.
The last step before campaign execution is the \textit{prune} step, where the collected data is translated into corresponding experiments.
Different data points from the trace that result in the same \textquote{fault-similarity class} (as used by Schirmeier~\autocite{schirmeierEfficientFaultInjectionbasedAssessment}) are removed from the campaign.
Two experiments belong to the same similarity class if the \textit{relevant} parts of their resulting simulator state are identical.