Skip to main navigation Skip to search Skip to main content

Towards Understanding Interactive Debugging

  • Fabio Petrillo
  • , Zephyrin Soh
  • , Foutse Khomh
  • , Marcelo Pimenta
  • , Carla Freitas
  • , Yann Gael Gueheneuc
  • Universidade Federal do Rio Grande do Sul
  • Polytechnique Montréal

Research output: Contribution to Book/Report types › Contribution to conference proceedings › peer-review

13 Citations (Scopus)

Abstract

Debugging is a laborious activity in which developers spend lot of time navigating through code, looking for starting points, and stepping through statements. Yet, although debuggers exist for 40 years now, there have been few research studies to understand this important and laborious activity. Indeed, to perform such a study, researchers need detailed information about the different steps of the interactive debugging process. In this paper, to help research studies on debugging and, thus, help improving our understanding of how developers debug systems using debuggers, we present the Swarm Debug Infrastructure (SDI), with which practitioners and researchers can collect and share data about developers' interactive debugging activities. We assess the effectiveness of the SDI through an experiment that aims to understand how developers apply interactive debugging on five true faults found in JabRef, toggling breakpoints and stepping code. Our study involved five freelancers and two student developers performing 19 bug location sessions. We collect videos recording and data about 6 hours of effective debugging activities. The data includes 110 breakpoints and near 7,000 invocations. We process the collected videos and data to answer five research questions showing that (1) there is no correlation between the number of invocations (respectively the number of breakpoints toggled) during a debugging session and the time spent on the debugging task, amp;#x03C1; =-0.039 (respectively 0.093). We also observed that (2) developers follow different debugging patterns and (3) there is no relation between numbers of breakpoints and expertise. However, (4) there is a strong negative correlation between time of the first breakpoint (amp;#x03C1; =-0.637), and the time spent on the task, suggesting that when developers toggle breakpoints carefully, they complete tasks faster than developers who toggle breakpoints too quickly. We conclude that the SDI allows collecting and sharing debugging data that can provide interesting insights about interactive debugging activities. We discuss some implications for tool developers and future debuggers.

Original languageEnglish
Title of host publicationProceedings - 2016 IEEE International Conference on Software Quality, Reliability and Security, QRS 2016
PublisherInstitute of Electrical and Electronics Engineers Inc.
Pages152-163
Number of pages12
ISBN (Electronic)9781509041275
DOIs
Publication statusPublished - 12 Oct 2016
Externally publishedYes
Event2nd IEEE International Conference on Software Quality, Reliability and Security, QRS 2016 - Vienna, Austria
Duration: 1 Aug 2016 → 3 Aug 2016

Publication series

NameProceedings - 2016 IEEE International Conference on Software Quality, Reliability and Security, QRS 2016

Conference

Conference2nd IEEE International Conference on Software Quality, Reliability and Security, QRS 2016
Country/TerritoryAustria
CityVienna
Period1/08/16 → 3/08/16

Keywords

  • Breakpoint
  • Interactive Debugging
  • Software Maintenance
  • Swarm Debugging

ASJC Scopus subject areas

  • Computer Networks and Communications
  • Software
  • Safety, Risk, Reliability and Quality

Fingerprint

Dive into the research topics of 'Towards Understanding Interactive Debugging'. These topics are generated from the title and abstract of the publication. Together, they form a unique fingerprint.

Cite this