Automatic debugging approaches for fixating failed system programs
Gulista Khan · 2021 · Asian Journal of Multidimensional Research
WASTE classifies this as Failed Experiment Report · AI classification, approximate
An experimental approach did not work as intended — learn what to avoid before investing the same effort.
Abstract (excerpt)
Fixing broken computer programs entails performing two basic debugging tasks: first, the programmer must recreate the problem; second, the programmer must identify the source of the failure. As a consequence of testing, software debugging…
Excerpt shown for reference under fair use — read the full paper at the publisher.
Hosted by the publisher — may require access.
About to run something similar?
Run an AI Precheck on your own design to catch failure modes like this one before you spend the time. Your first desk check is free.
Related failures
The Two-pore channel (TPC) interactome unmasks isoform-specific roles for TPCs in endolysosomal morphology and cell pigmentation
Failed Experiment ReportA Markov-Middleton Model for Bursty Impulsive Noise: Modeling and Receiver Design
Failed Experiment ReportThe Reference of Proper Names: Testing Usage and Intuitions
Failed Experiment ReportAn investigation of self‐efficacy crossover between mentors and protégés within mentoring dyads
Failed Experiment ReportLymphatic endothelial cells are a replicative niche for Mycobacterium tuberculosis
Failed Experiment ReportStatistically comparing EEG / MEG waveforms through successive significant univariate tests: How bad can it be?
WASTE indexes this work — it does not host or republish it. Failure-type classification is automated and approximate.
Metadata source: Crossref · DOI 10.5958/2278-4853.2021.00980.0