Reference : Locating Faults with Program Slicing: An Empirical Analysis
Scientific journals : Article
Engineering, computing & technology : Computer science
Security, Reliability and Trust
http://hdl.handle.net/10993/52016
Locating Faults with Program Slicing: An Empirical Analysis
English
Soremekun, Ezekiel mailto [University of Luxembourg > Interdisciplinary Centre for Security, Reliability and Trust (SNT) > SerVal >]
Kirschner, Lukas mailto [CISPA - Helmholtz Center for Information Security, Saarbrücken, Germany]
Böhme, Marcel mailto [Monash University, Melbourne, Australia]
Zeller, Andreas mailto [CISPA - Helmholtz Center for Information Security, Saarbrücken, Germany]
1-Apr-2021
Empirical Software Engineering
Kluwer Academic Publishers
26
3
1-45
Yes
International
1382-3256
1573-7616
Netherlands
[en] Software engineering ; Software debugging ; Software testing ; Automated fault localization ; Program slicing ; Statistical debugging
[en] Statistical fault localization is an easily deployed technique for quickly determining candidates for faulty code locations. If a human programmer has to search the fault beyond the top candidate locations, though, more traditional techniques of following dependencies along dynamic slices may be better suited. In a large study of 457 bugs (369 single faults and 88 multiple faults) in 46 open source C programs, we compare the effectiveness of statistical fault localization against dynamic slicing. For single faults, we find that dynamic slicing was eight percentage points more effective than the best performing statistical debugging formula; for 66% of the bugs, dynamic slicing finds the fault earlier than the best performing statistical debugging formula. In our evaluation, dynamic slicing is more effective for programs with single fault, but statistical debugging performs better on multiple faults. Best results, however, are obtained by a hybrid approach: If programmers first examine at most the top five most suspicious locations from statistical debugging, and then switch to dynamic slices, on average, they will need to examine 15% (30 lines) of the code. These findings hold for 18 most effective statistical debugging formulas and our results are independent of the number of faults (i.e. single or multiple faults) and error type (i.e. artificial or real errors).
http://hdl.handle.net/10993/52016
10.1007/s10664-020-09931-7

File(s) associated to this reference

Fulltext file(s):

FileCommentaryVersionSizeAccess
Open access
s10664-020-09931-7.pdfPublisher postprint3.99 MBView/Open

Bookmark and Share SFX Query

All documents in ORBilu are protected by a user license.