Lightweight runtime checking of C programs with RTC

Milewicz, Reed; Vanka, Rajesh; Tuck, James; Quinlan, Daniel J.; Pirkelbauer, Peter

doi:10.1016/j.cl.2016.01.001

Search citation statements

Order By: Relevance

Paper Sections

Select...

Future Work1

Citation Types

Supporting

Mentioning

Contrasting

Year Published

2017

Publication Types

Select...

Other2

Relationship

Self Cite0

Independent2

Authors

Journals

Cited by 2 publications

(1 citation statement)

References 38 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Handling breakpoints is costly [6] and handling watchpoints even more. Code injection could provide better e ciency [31,32] by limiting round trips between the debugger and the program would to the bare minimum (for example, when the scenario requires the execution to be suspended to let the user interact with the debugger) while keeping the current exibility of the approach.…”

Section: Future Workmentioning

confidence: 99%

Interactive Runtime Verification

Jakse¹,

Falcone²,

Méhaut³

et al. 2017

Preprint

View full text Add to dashboard Cite

Monitoring is the study of a system at runtime, looking for input and output events to discover, check or enforce behavioral properties. Interactive debugging is the study of a system at runtime in order to discover and understand its bugs and x them, inspecting interactively its internal state.Interactive Runtime Veri cation (i-RV) combines monitoring and interactive debugging. We de ne an e cient and convenient way to check behavioral properties automatically on a program using a debugger. We aim at helping bug discovery while keeping the classical debugging techniques and interactivity, which allow understanding and xing bugs.CCS Concepts: •Software and its engineering → Software testing and debugging;

show abstract

Section: Future Workmentioning

confidence: 99%