什么是“bug”?论软件研究中的主观性、认知权力及其影响
What is a "bug"? On subjectivity, epistemic power, and implications for software research
AI总结:
本文探讨了软件研究中“bug”定义的主观性与认知权力问题,指出在缺乏完整形式化规约时,现有定义常依赖不完美的代理,并分析了这种模糊性对软件工程研究的影响。
摘要:
软件研究和实践中大量的精力都花在了bug上。寻找、报告、跟踪、分类、尝试自动修复以及检测“bug气味”——这些占据了大型项目大量时间和开发成本,也是软件工程、编程语言等领域研究人员的重要兴趣所在。但是,到底什么是bug?虽然段错误很少让人高兴,但大多数bug并没有那么界限分明。根据《牛津英语词典》,自1870年代起,“bug”一词就一直是工程“缺陷”的口语表达。大多数现代面向软件的定义都指向开发者意图与程序实际行为之间的脱节。形式化验证自诞生起就发展出了识别与形式化规约偏离的方法,这些规约被期望能或多或少完全编码预期行为。然而,软件很少伴随完整的形式化规约,这种意图通常被视为隐式的或最多是部分记录的。国际软件测试认证委员会写道:“人可能会犯错,从而在程序代码或文档中产生缺陷。如果代码中的缺陷被执行,系统可能无法完成应做之事(或做了不该做的事),导致失效。缺陷可能导致失效,但并非所有缺陷都会如此。”大多数来源放弃了这种精确性。有影响力的论文《Finding bugs is easy》开篇就说“bug模式是经常出错的代码习惯用法”——却没有特别详细说明。其他工作则依赖于不完美的实际规约代理。例如,在自动程序修复研究中,bug对应于失败的测试用例:当测试通过时,bug就被视为已修复。然而,当我们审视这些相当直接的定义时,它们开始崩塌……
英文摘要:
Considerable effort in software research and practice is spent on bugs. Finding, reporting, tracking, triaging, attempting to fix them automatically, detecting "bug smells" -these comprise a substantial portion of large projects' time and development cost, and are of significant interest to researchers in Software Engineering, Programming Languages, and beyond. But, what is a bug, exactly? While segmentation faults rarely spark joy, most bugs are not so clear cut. Per the Oxford English Dictionary, the word "bug" has been a colloquialism for an engineering "defect" at least since the 1870s. Most modern software-oriented definitions speak to a disconnect between what a developer intended and what a program actually does. Formal verification, from its inception, has developed means to identify deviations from a formal specification, expected to more or less fully encode desired behavior. However, software is rarely accompanied by full and formal specifications, and this intention is instead treated as implicit or partially-documented at best. The International Software Testing Qualifications board writes: "A human being can make an error (mistake), which produces a defect (fault, bug) in the program code, or in a document. If a defect in code is executed, the system may fail to do what it should do (or do something it shouldn't), causing a failure. Defects may result in failures, but not all [do]". Most sources forsake this precision. The influential paper "Finding bugs is easy" begins by saying "bug patterns are code idioms that are often errors"-with no particular elaboration. Other work relies on imperfect practical proxies for specifications. For example, in automatic program repair research, a bug corresponds to a failing test case: when the test passes, the bug is considered fixed. However, when we interrogate fairly straightforward definitions, they start to break down...
机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。