Null Check Analysis


Autoria(s): Osman, Haidar
Data(s)

01/07/2015

Resumo

Null dereferencing is one of the most frequent bugs in Java systems causing programs to crash due to the uncaught NullPointerException. Developers often fix this bug by introducing a guard (i.e., null check) on the potentially-null objects before using them. In this paper we investigate the null checks in 717 open-source Java systems to understand when and why developers introduce null checks. We find that 35 of the if-statements are null checks. A deeper investigation shows that 71 of the checked-for-null objects are returned from method calls. This indicates that null checks have a serious impact on performance and that developers introduce null checks when they use methods that return null.

Formato

application/pdf

Identificador

http://boris.unibe.ch/82288/1/Osma15a.pdf

Osman, Haidar (July 2015). Null Check Analysis. In: Extended Abstracts of the Eighth Seminar on Advanced Techniques and Tools for Software Evolution (SATToSE 2015). Mons, Belgium. 06.-08.07.2015.

doi:10.7892/boris.82288

Idioma(s)

eng

Relação

http://boris.unibe.ch/82288/

http://scg.unibe.ch/archive/papers/Osma15a.pdf

Direitos

info:eu-repo/semantics/restrictedAccess

Fonte

Osman, Haidar (July 2015). Null Check Analysis. In: Extended Abstracts of the Eighth Seminar on Advanced Techniques and Tools for Software Evolution (SATToSE 2015). Mons, Belgium. 06.-08.07.2015.

Palavras-Chave #000 Computer science, knowledge & systems #510 Mathematics
Tipo

info:eu-repo/semantics/conferenceObject

info:eu-repo/semantics/publishedVersion

PeerReviewed