How do fixes become bugs? A comprehensive characteristic study on incorrect fixes in commercial and open source operating systems

SIGSOFT/FSE 2011 - Proceedings of the 19th ACM SIGSOFT Symposium on Foundations of Software Engineering

Volumn , Issue , 2011, Pages 26-36

  Yin, Zuoning ^a   Yuan, Ding ^a   Zhou, Yuanyuan ^b   Pasupathy, Shankar ^c   Bairavasundaram, Lakshmi ^c  

^a University of Illinois at Urbana Champaign   (United States)

^b UNIVERSITY OF CALIFORNIA   (United States)

^c Network Appliance Inc   (United States)

Author keywords

Bug fixing; Human factor; Incorrect fixes; Software bugs; Testing

Indexed keywords

BUG FIXES; BUG-FIXING; COMMERCIAL SOFTWARE; DEVELOPMENT PROCESS; END USERS; FREEBSD; HUMAN FACTOR; HUMAN REASON; INCORRECT FIXES; OPEN SOURCE OPERATING SYSTEMS; REVIEWING PROCESS; SOFTWARE BUG; SOFTWARE BUGS; SOFTWARE VENDORS; SOURCE CODES; SYSTEM RELIABILITY;

BUILDING CODES; COMPUTER OPERATING SYSTEMS; HUMAN ENGINEERING; PROGRAM DEBUGGING; SOFTWARE ENGINEERING; SOFTWARE RELIABILITY; TESTING;

OPEN SYSTEMS;

EID: 80053200028     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/2025113.2025121     Document Type: Conference Paper

References (44)

1. Microsoft security bulletin. http://www.microsoft.com/technet/security/ current.aspx.
2. After buggy patch, criminals exploit Windows flaw. http://www.infoworld. com/d/security-central/after-buggy-patch-criminals-exploit-windows-flaw-848.
3. J. Anvik, L. Hiew, and G. C. Murphy. Who should fix this bug? In ICSE'06.
4. Apple updates leopard again. http://voices.washingtonpost.com/ fasterforward/2008/02/apple-updates-leopardagain.html.
5. A. Bachmann, C. Bird, F. Rahman, P. Devanbu, and A. Bernstein. The missing links: Bugs and bug-fix commits. In FSE'10.
6. M. J. Baker and S. G. Eick. Visualizing software systems. In ICSE'94.
7. C. Bird, N. Nagappan, P. Devanbu, H. Gall, and B. Murphy. Does distributed development affect software quality? An empirical case study of Windows Vista. In ICSE'09.
8. Buggy McAfee update whacks Windows XP PCs. http://news.cnet.com/8301- 1009-3-20003074-83.html.
9. D. Engler and K. Ashcraft. RacerX: effective, static detection of race conditions and deadlocks. In SOSP'03.
10. D. Engler, D. Y. Chen, S. Hallem, A. Chou, and B. Chelf. Bugs as deviant behavior: a general approach to inferring errors in systems code. In SOSP'01.
11. M. Fischer, M. Pinzger, and H. Gall. Populating a release history database from version control and bug tracking systems. In ICSM'03.
12. K. B. Gallagher and J. R. Lyle. Using program slicing in software maintenance. IEEE Transactions on Software Engineering, 17(8):751-761, 1991.
13. Z. Gu, E. T.Barr, D. J.Hamilton, and Z. Su. Has the bug really been fixed? In ICSE'10.
14. M. Harman, D. Binkley, and S. Danicic. Amorphous program slicing. Journal of Systems and Software, 68(1):45-64, October 2003.
15. Intel reissues buggy patch. http://www.pcworld.com/businesscenter/ article/126918/rss.html.
16. D. Kawrykow and M. P. Robillard. Non-essential changes in version histories. In ICSE'11, May 2011.
17. S. Kim, K. Pan, and J. E. James Whitehead. Memories of bug fixes. In FSE'06, November 2006.
18. S. Kim, E. J. Whitehead, Jr., and Y. Zhang. Classifying Software Changes: Clean or Buggy? IEEE Trans. Software Engineering, 34(2):181-196, March 2008. (Pubitemid 351583527)
19. Z. Li, L. Tan, X. Wang, S. Lu, Y. Zhou, and C. Zhai. Have things changed now? An empirical study of bug characteristics in modern open source software. In ASID'06.
20. Z. Li and Y. Zhou. PR-Miner: Automatically extracting implicit programming rules and detecting violations in large software code. In FSE'05.
21. S. Lu, S. Park, E. Seo, and Y. Zhou. Learning from mistakes - a comprehensive study on real world concurrency bug characteristics. In ASPLOS, March 2008.
22. McAfee to reimburse customers for bad patch. http://www.computerworlduk. com/technology/security-products/prevention/news/index.cfm?newsId=20005.
23. S. McCamant and M. D. Ernst. Predicting problems caused by component upgrades. In FSE'03.
24. D. W. McDonald and M. S. Ackerman. Expertise recommender: a flexible recommendation system and architecture. In CSCW'00.
25. A. Meneely and L. Williams. Secure open source collaboration: An empirical study of linus's law. In CCS'09.
26. A. Mockus and D. M. Weiss. Predicting risk of software changes. Bell Labs Technical Journal, 5:169-180, 2000.
27. N. Nagappan, B. Murphy, and V. R. Basili. The influence of organizational structure on software quality. In ICSE'08.
28. T. T. Nguyen, H. A. Nguyen, N. H. Pham, J. Al-Kofahi, and T. N. Nguyen. Recurring bug fixes in object-oriented programs. In ICSE'10, May 2010.
29. A. Orso, N. Shi, and M. J. Harrold. Scaling regression testing to large software systems. In FSE'04.
30. Y. Padioleau, J. Lawall, R. R. Hansen, and G. Muller. Documenting and automating collateral evolutions in linux device drivers. In Eurosys'08.
31. K. Pan, S. Kim, and J. E. James Whitehead. Toward an understanding of bug fix patterns. Empirical Software Engineering, 14(3):286-315, November 2009.
32. J. H. Perkins, S. Kim, S. Larseng, S. Amarasinghe, J. Bachrach, M. Carbin, C. Pachecod, F. Sherwood, S. Sidiroglou, G. Sullivan, W.-F. Wong, Y. Zibin, M. D. Ernst, and M. Rinard. Automatically patching errors in deployed software. In SOSP'09, October 2009.
33. R. Purushothaman and D. E. Perry. Towards understanding the rhetoric of small changes. In MSR'04.
34. F. Rahman and P. Devanbu. Ownership and experience in fix-inducing code. In UC Davis Department of Computer Science, Technical Report CSE-2010-4, 2010.
35. G. Rothermel, R. H. Untch, C. Chu, and M. J. Harrold. Prioritizing test cases for regression testing. IEEE Transactions on Software Engineering, 27:929-948, 2001. (Pubitemid 33048252)
36. J. Śliwerski, T. Zimmermann, and A. Zeller. When do changes induce fixes? In MSR'05.
37. J. Śliwerski, T. Zimmermann, and A. Zeller. Hatari: Raising risk awareness (research demonstration). In FSE'05, September 2005.
38. L. Tan, D. Yuan, and Y. Zhou./* icomment: Bugs or bad comments? */. In SOSP, October 2007.
39. J. Tucek, W. Xiong, and Y. Zhou. Efficient online validationwith delta execution. In ASPLOS'09.
40. D. Čubranić and G. C. Murphy. Hipikat: Recommending pertinent software development artifacts. In ICSE'03.
41. M. Weiser. Program slicing. In ICSE'83.
42. Z. Yin, M. Caesar, and Y. Zhou. Towards understanding bugs in open source router software. ACM SIGCOMM Computer Communication Review, 40(3):34-40, July 2010.
43. D. Yuan, H. Mai, W. Xiong, L. Tan, Y. Zhou, and S. Pasupathy. Sherlog: error diagnosis by connecting clues from run-time logs. In ASPLOS'10.
44. A. Zeller. Yesterday, my program worked. today, it does not. why? In FSE'99.