2017 32nd IEEE/ACM International Conference on Automated Software Engineering (ASE) 2017
DOI: 10.1109/ase.2017.8115650
|View full text |Cite
|
Sign up to set email alerts
|

TrEKer: Tracing error propagation in operating system kernels

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
7
0

Year Published

2018
2018
2021
2021

Publication Types

Select...
4
1

Relationship

2
3

Authors

Journals

citations
Cited by 6 publications
(7 citation statements)
references
References 41 publications
0
7
0
Order By: Relevance
“…Our work makes use of TrEKer [10], a technique for tracing error propagation in OS kernels using execution traces at the granularity of individual memory accesses.…”
Section: Error Propagation Analysismentioning
confidence: 99%
See 1 more Smart Citation
“…Our work makes use of TrEKer [10], a technique for tracing error propagation in OS kernels using execution traces at the granularity of individual memory accesses.…”
Section: Error Propagation Analysismentioning
confidence: 99%
“…Prior work has attempted to tackle this issue by introducing additional instrumentation to the faulty module for tracing the modifications made by the faulty module either to the system state or to externally visible parts of its own state [10]. These modifications can then be compared to those made by the non-faulty version of the same module, with the assumption that instances in which the behavior of the faulty version diverges from the non-faulty version constitute potential error propagation.…”
mentioning
confidence: 99%
“…6. Reversibility formula build time in seconds (log scale) for blackscholes traces with different input sizes and numbers of threads pose, we generated execution traces of the benchmark with inputs of varying size (2,4,8,16,32 inputs) and varying numbers of threads (1,2,4,6,8,12,16) handling these inputs. We have repeated the reversibility check four times for each input/thread count combination to account for execution time variations.…”
Section: F Rq 4: Tracesanitizer Overheadmentioning
confidence: 99%
“…EPA analyzes how software faults affect program control and data flow at run time. It has many uses such as error detector placement [1], [2] and robustness testing [3]. EPA is typically performed by injecting faults into the program, and comparing the fault-affected (faulty run) against the fault-free (golden run) execution traces, i.e., records of which program instructions have been executed in which order.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation