Skip to main navigation Skip to search Skip to main content

Deterministic replay for multi-core VxWorks applications

  • Beihang University
  • CAS - Institute of Software

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

Debugging is an important and yet expensive activity in software development. With the adoption of multi-core computing platform, the debugging of multi-core bugs on real-time platform becomes challenging. Those multi-core concurrency bugs are often called Heisenbugs, because they manifest randomly during replay. As a result, it would be difficult for a programmer to use cyclic debugging to locate the fault. In this work, we present a deterministic replay tool for multi-core real-time VxWorks applications. We combine static analysis and source code instrumentation to help record interleaved access to shared memory for multi-tasking VxWorks applications. Our experimental results show that our tool can effectively reply multi-core real-time VxWorks applications with reasonable overhead.

Original languageEnglish
Title of host publicationProceedings - 4th International Conference on Dependable Systems and Their Applications, DSA 2017
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages118-125
Number of pages8
ISBN (Electronic)9781538636909
DOIs
StatePublished - 2 Jul 2017
Event4th International Conference on Dependable Systems and Their Applications, DSA 2017 - Beijing, China
Duration: 31 Oct 20172 Nov 2017

Publication series

NameProceedings - 4th International Conference on Dependable Systems and Their Applications, DSA 2017
Volume2018-January

Conference

Conference4th International Conference on Dependable Systems and Their Applications, DSA 2017
Country/TerritoryChina
CityBeijing
Period31/10/172/11/17

Keywords

  • VxWorks
  • deterministic replay
  • multi-core debugging

Fingerprint

Dive into the research topics of 'Deterministic replay for multi-core VxWorks applications'. Together they form a unique fingerprint.

Cite this