@INPROCEEDINGS{Petrillo16-QRS-InteractiveDebugging,
   AUTHOR       = {Fabio Petrillo and Z�phyrin Soh and Foutse Khomh and 
      Marcelo Soares Pimenta and Carla Maria Dal Sasso Freitas and 
      Yann-Ga�l Gu�h�neuc},
   BOOKTITLE    = {Proceedings of the 24<sup>th</sup> International Conference on Software Quality, Reliability, and Security (QRS)},
   TITLE        = {Towards Understanding Interactive Debugging},
   YEAR         = {2016},
   OPTADDRESS   = {},
   OPTCROSSREF  = {},
   EDITOR       = {Yves Le Traon and Zhenyu Chen},
   MONTH        = {August},
   NOTE         = {10 pages.},
   OPTNUMBER    = {},
   OPTORGANIZATION = {},
   PAGES        = {152--163},
   PUBLISHER    = {IEEE CS Press},
   OPTSERIES    = {},
   OPTVOLUME    = {},
   KEYWORDS     = {Topic: <b>Program comprehension</b>, Venue: <c>QRS</c>},
   URL          = {http://www.ptidej.net/publications/documents/QRS16.doc.pdf},
   PDF          = {http://www.ptidej.net/publications/documents/QRS16.ppt.pdf},
   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, p = -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 (p = 
      -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.}
}

{"_id":"oac3YFFmLj9c6bQbE","bibbaseid":"petrillo-soh-khomh-pimenta-freitas-guhneuc-towardsunderstandinginteractivedebugging-2016","author_short":["Petrillo, F.","Soh, Z.","Khomh, F.","Pimenta, M. S.","Freitas, C. M. D. S.","Gu�h�neuc, Y."],"bibdata":{"bibtype":"inproceedings","type":"inproceedings","author":[{"firstnames":["Fabio"],"propositions":[],"lastnames":["Petrillo"],"suffixes":[]},{"firstnames":["Z�phyrin"],"propositions":[],"lastnames":["Soh"],"suffixes":[]},{"firstnames":["Foutse"],"propositions":[],"lastnames":["Khomh"],"suffixes":[]},{"firstnames":["Marcelo","Soares"],"propositions":[],"lastnames":["Pimenta"],"suffixes":[]},{"firstnames":["Carla","Maria","Dal","Sasso"],"propositions":[],"lastnames":["Freitas"],"suffixes":[]},{"firstnames":["Yann-Ga�l"],"propositions":[],"lastnames":["Gu�h�neuc"],"suffixes":[]}],"booktitle":"Proceedings of the 24^th International Conference on Software Quality, Reliability, and Security (QRS)","title":"Towards Understanding Interactive Debugging","year":"2016","optaddress":"","optcrossref":"","editor":[{"firstnames":["Yves","Le"],"propositions":[],"lastnames":["Traon"],"suffixes":[]},{"firstnames":["Zhenyu"],"propositions":[],"lastnames":["Chen"],"suffixes":[]}],"month":"August","note":"10 pages.","optnumber":"","optorganization":"","pages":"152–163","publisher":"IEEE CS Press","optseries":"","optvolume":"","keywords":"Topic: <b>Program comprehension</b>, Venue: <c>QRS</c>","url":"http://www.ptidej.net/publications/documents/QRS16.doc.pdf","pdf":"http://www.ptidej.net/publications/documents/QRS16.ppt.pdf","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, p = -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 (p = -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.","bibtex":"@INPROCEEDINGS{Petrillo16-QRS-InteractiveDebugging,\r\n AUTHOR = {Fabio Petrillo and Z�phyrin Soh and Foutse Khomh and \r\n Marcelo Soares Pimenta and Carla Maria Dal Sasso Freitas and \r\n Yann-Ga�l Gu�h�neuc},\r\n BOOKTITLE = {Proceedings of the 24^th International Conference on Software Quality, Reliability, and Security (QRS)},\r\n TITLE = {Towards Understanding Interactive Debugging},\r\n YEAR = {2016},\r\n OPTADDRESS = {},\r\n OPTCROSSREF = {},\r\n EDITOR = {Yves Le Traon and Zhenyu Chen},\r\n MONTH = {August},\r\n NOTE = {10 pages.},\r\n OPTNUMBER = {},\r\n OPTORGANIZATION = {},\r\n PAGES = {152--163},\r\n PUBLISHER = {IEEE CS Press},\r\n OPTSERIES = {},\r\n OPTVOLUME = {},\r\n KEYWORDS = {Topic: <b>Program comprehension</b>, Venue: <c>QRS</c>},\r\n URL = {http://www.ptidej.net/publications/documents/QRS16.doc.pdf},\r\n PDF = {http://www.ptidej.net/publications/documents/QRS16.ppt.pdf},\r\n ABSTRACT = {Debugging is a laborious activity in which developers \r\n spend lot of time navigating through code, looking for starting \r\n points, and stepping through statements. Yet, although debuggers \r\n exist for 40 years now, there have been few research studies to \r\n understand this important and laborious activity. Indeed, to perform \r\n such a study, researchers need detailed information about the \r\n different steps of the interactive debugging process. In this paper, \r\n to help research studies on debugging and, thus, help improving our \r\n understanding of how developers debug systems using debuggers, we \r\n present the Swarm Debug Infrastructure (SDI), with which \r\n practitioners and researchers can collect and share data about \r\n developers' interactive debugging activities. We assess the \r\n effectiveness of the SDI through an experiment that aims to \r\n understand how developers apply interactive debugging on five true \r\n faults found in JabRef, toggling breakpoints and stepping code. Our \r\n study involved five freelancers and two student developers performing \r\n 19 bug location sessions. We collect videos recording and data about \r\n 6 hours of effective debugging activities. The data includes 110 \r\n breakpoints and near 7,000 invocations. We process the collected \r\n videos and data to answer five research questions showing that (1) \r\n there is no correlation between the number of invocations \r\n (respectively the number of breakpoints toggled) during a debugging \r\n session and the time spent on the debugging task, p = -0.039 \r\n (respectively 0.093). We also observed that (2) developers follow \r\n different debugging patterns and (3) there is no relation between \r\n numbers of breakpoints and expertise. However, (4) there is a strong \r\n negative correlation between time of the first breakpoint (p = \r\n -0.637), and the time spent on the task, suggesting that when \r\n developers toggle breakpoints carefully, they complete tasks faster \r\n than developers who toggle breakpoints too quickly. We conclude that \r\n the SDI allows collecting and sharing debugging data that can provide \r\n interesting insights about interactive debugging activities. We \r\n discuss some implications for tool developers and future debuggers.}\r\n}\r\n\r\n","author_short":["Petrillo, F.","Soh, Z.","Khomh, F.","Pimenta, M. S.","Freitas, C. M. D. S.","Gu�h�neuc, Y."],"editor_short":["Traon, Y. L.","Chen, Z."],"key":"Petrillo16-QRS-InteractiveDebugging","id":"Petrillo16-QRS-InteractiveDebugging","bibbaseid":"petrillo-soh-khomh-pimenta-freitas-guhneuc-towardsunderstandinginteractivedebugging-2016","role":"author","urls":{"Paper":"http://www.ptidej.net/publications/documents/QRS16.doc.pdf"},"keyword":["Topic: <b>Program comprehension</b>","Venue: <c>QRS</c>"],"metadata":{"authorlinks":{}}},"bibtype":"inproceedings","biburl":"http://www.yann-gael.gueheneuc.net/Work/Publications/Biblio/complete-bibliography.bib","dataSources":["KfXmPhaoCuAwjS2aX","SCHo5ZZkXuxNNaMME","8vn5MSGYWB4fAx9Z4"],"keywords":["topic: <b>program comprehension</b>","venue: <c>qrs</c>"],"search_terms":["towards","understanding","interactive","debugging","petrillo","soh","khomh","pimenta","freitas","gu�h�neuc"],"title":"Towards Understanding Interactive Debugging","year":2016}