Reference : Mining Android Crash Fixes in the Absence of Issue- and Change-Tracking Systems
Scientific congresses, symposiums and conference proceedings : Unpublished conference
Engineering, computing & technology : Computer science
Security, Reliability and Trust
http://hdl.handle.net/10993/41499
Mining Android Crash Fixes in the Absence of Issue- and Change-Tracking Systems
English
Kong, Pingfan mailto [University of Luxembourg > Interdisciplinary Centre for Security, Reliability and Trust (SNT) > >]
li, li mailto [Monash University]
Gao, Jun mailto [University of Luxembourg > Interdisciplinary Center for Security, Reliability and Trust]
Bissyande, Tegawendé François D Assise mailto [University of Luxembourg > Interdisciplinary Centre for Security, Reliability and Trust (SNT) > >]
Klein, Jacques mailto [University of Luxembourg > Interdisciplinary Centre for Security, Reliability and Trust (SNT) > Computer Science and Communications Research Unit (CSC) >]
15-Jul-2019
@inproceedings{kong2019mining,
title={Mining Android crash fixes in the absence of issue-and change-tracking systems},
author={Kong, Pingfan and Li, Li and Gao, Jun and Bissyand{\'e}, Tegawend{\'e} F and Klein, Jacques},
booktitle={Proceedings of the 28th ACM SIGSOFT International Symposium on Software Testing and Analysis},
pages={78--89},
year={2019}
}
Yes
No
International
The 28th International Symposium on Software Testing and Analysis
from 15-07-2019 to 19-07-2019
ACM
Beijing
China
[en] Android ; crash ; testing ; debugging ; mining software repository
[en] Android apps are prone to crash. This often arises from the misuse of Android framework APIs, making it harder to debug since official Android documentation does not discuss thoroughly potential exceptions.Recently, the program repair community has also started to investigate the possibility to fix crashes automatically. Current results, however, apply to limited example cases. In both scenarios of repair, the main issue is the need for more example data to drive the fix processes due to the high cost in time and effort needed to collect and identify fix examples. We propose in this work a scalable approach, CraftDroid, to mine crash fixes by leveraging a set of 28 thousand carefully reconstructed app lineages from app markets, without the need for the app source code or issue reports. We developed a replicative testing approach that locates fixes among app versions which output different runtime logs with the exact same test inputs. Overall, we have mined 104 relevant crash fixes, further abstracted 17 fine-grained fix templates that are demonstrated to be effective for patching crashed apks. Finally, we release ReCBench, a benchmark consisting of 200 crashed apks and the crash replication scripts, which the community can explore for evaluating generated crash-inducing bug patches.
Interdisciplinary Centre for Security, Reliability and Trust (SnT) > Security Design and Validation Research Group (SerVal)
Fonds National de la Recherche - FnR
Researchers ; Students
http://hdl.handle.net/10993/41499
10.1145/3293882.3330572
https://dl.acm.org/doi/10.1145/3293882.3330572
FnR ; FNR11693861 > Jacques Klein > CHARACTERIZE > Characterization of Malicious Code in Mobile Apps: Towards Accurate and Explainable Malware Detection > 01/06/2018 > 31/05/2021 > 2017

File(s) associated to this reference

Fulltext file(s):

FileCommentaryVersionSizeAccess
Open access
article.pdfPublisher postprint1.16 MBView/Open

Bookmark and Share SFX Query

All documents in ORBilu are protected by a user license.