{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,7,4]],"date-time":"2025-07-04T16:03:09Z","timestamp":1751644989442,"version":"3.41.0"},"reference-count":0,"publisher":"Association for Computing Machinery (ACM)","issue":"1","license":[{"start":{"date-parts":[[1989,8,1]],"date-time":"1989-08-01T00:00:00Z","timestamp":617932800000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["SIGCHI Bull."],"published-print":{"date-parts":[[1989,8]]},"abstract":"<jats:p>This paper presents a series of four experiments investigating\nstudents' debugging of LISP programs. The experiments involve a\npopulation of subjects who know LISP reasonably well and whose\nerrors are best classified as slips (Brown &amp; Van Lehn, 1980).\nThat is, students are unlikely to repeat the same errors either\nwithin their program or across programs (Experiment 1). That the\nstudents understand LISP is also reflected in their debugging\nbehavior: students can usually fix a bug once they locate it.\nStudents' difficulties are instead in locating the errorful line of\ncode. We observe that students use a variety of bug-location\nstrategies during debugging (Experiment 2) and that the choice of\nstrategy differs depending on whether students are debugging their\nown programs or other students' programs (Experiment 3). In\naddition, we observe that although the different bug-location\nstrategies affect which lines of a program are searched, once\nstudents decide on a line, their ability to judge whether or not\nthe line is correct and their ability to correct an error are not\nsubstantially affected by the strategy being used to locate the\nline (Experiment 4). Finally, we argue that our results have\nimplications not only for debugging in other computer languages,\nbut for the general processes involved in troubleshooting as well.<\/jats:p>","DOI":"10.1145\/67880.1046598","type":"journal-article","created":{"date-parts":[[2007,1,17]],"date-time":"2007-01-17T18:32:02Z","timestamp":1169058722000},"page":"123","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":3,"title":["Debugging: An Analysis of Bug-Location Strategies (Abstract Only)"],"prefix":"10.1145","volume":"21","author":[{"given":"Irvin R.","family":"Katz","sequence":"first","affiliation":[],"role":[{"role":"author","vocabulary":"crossref"}]},{"given":"John R.","family":"Anderson","sequence":"additional","affiliation":[],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"320","published-online":{"date-parts":[[1989,8]]},"container-title":["ACM SIGCHI Bulletin"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/67880.1046598","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/67880.1046598","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T21:15:00Z","timestamp":1750281300000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/67880.1046598"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[1989,8]]},"references-count":0,"journal-issue":{"issue":"1","published-print":{"date-parts":[[1989,8]]}},"alternative-id":["10.1145\/67880.1046598"],"URL":"https:\/\/doi.org\/10.1145\/67880.1046598","relation":{},"ISSN":["0736-6906"],"issn-type":[{"type":"print","value":"0736-6906"}],"subject":[],"published":{"date-parts":[[1989,8]]},"assertion":[{"value":"1989-08-01","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}