Control-flow checking by software signatures
By Nahmsuk Oh, Philip P. Shirvani, Edward Joseph McCluskey Jr.. IEEE Transactions on Reliability, 2002
615 citations recorded by the source corpus.
Subfields: Artificial Intelligence, Computer Networks and Communications, Electrical and Electronic Engineering
View Paper: https://www.semanticscholar.org/paper/eca217cfa0c878c9685235ab1ca39ead34946b63
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Artificial Intelligence
In Computer Networks and Communications
- Ram Rangan
- George A. Reis
- Neil Vachharajani
- David I. August
- Jonathan T.-Y. Chang
- Nahmsuk Oh
- Edward Joseph McCluskey Jr.
- Philip P. Shirvani
In Electrical and Electronic Engineering
- Ram Rangan
- George A. Reis
- Neil Vachharajani
- David I. August
- Jonathan T.-Y. Chang
- Nahmsuk Oh
- Edward Joseph McCluskey Jr.
- Philip P. Shirvani
Citations in the corpus
- SWIFT: software implemented fault tolerance (2005, methodology): “In this section, we will describe the foundation of this work, EDDI [12], discuss extending EDDI with control-flow checking with software signatures [11], and finally introduce the novel extensions that comprise SWIFT.”
- Design for soft error mitigation (2005, background): “Of course, the cost is reduced if control flow checking [19], [22], [23] alone is used, but the protection is incomplete.”
- Error detection by duplicated instructions in super-scalar processors (2002, methodology): “On the other hand, Control Flow Checking by Software Signatures (CFCSS) [21] is a pure software technique for checking control flow errors.”