[软件自动修复领域] 偏实证分析类论文阅读-2019年8月9日

文章目录

    • 前言
    • 论文列表
      • Better Test Cases for Better Automated Program Repair
      • A Theoretical and Empirical Analysis of Program Spectra Diagnosability
      • An empirical study on TensorFlow program bugs
      • An Empirical Study on Real Bug Fixes
      • LogTracker: Learning Log Revision Behaviors Proactively from Software Evolution History
      • Fine-grained and accurate source code differencing
    • 小结

标题:[软件自动修复领域] 偏实证分析类论文阅读-2019年8月9日

前言

写这类博客的目的:
1)保持自己对领域内前沿研究的了解;
2)与诸君分享所看文章(有些文章确实挺经典的,值得一读)。
故而,希望每日一作。苟日新,日日新,又日新。

论文列表

Better Test Cases for Better Automated Program Repair

来源:自己之前关注的。

引用:
@inproceedings{yang_better_2017,
title = {Better test cases for better automated program repair},
booktitle = {Proceedings of the 2017 11th {Joint} {Meeting} on {Foundations} of {Software} {Engineering}},
publisher = {ACM},
author = {Yang, Jinqiu and Zhikhartsev, Alexey and Liu, Yuefei and Tan, Lin},
year = {2017},
pages = {831–841},
file = {Full Text:D:\software\zotero\pdf-download-path\storage\7LNTE8EC\Yang 等。 - 2017 - Better test cases for better automated program rep.pdf:application/pdf;Snapshot:D:\software\zotero\pdf-download-path\storage\ILP9SJ36\citation.html:text/html}
}

框架:
3 Approach

  • Overview.(作流程图)
  • Challenges.(摆难题)
  • 3.1 Generating New Test Cases Using Fuzz Testing
  • 3.2 Generating Memory-Safety Oracles(具体的技术)
  • 3.3 Measuring the Overfitness of a Patch Using an Overfitness Metric (O-measure)(顺手提了一个O-measure 度量指标。还用了很多理论证明。。这里我没太看明白,定义倒是看懂了,但是后续证明没懂。还需细看)
  • 3.4 An Optimized Setting of Opad

4 EVALUATION
Experimental Setup.
RQ1: How many overfitted patches does Opad filter out?

  • Motivation.
  • Approach.
  • Results.

5 THREATS TO VALIDITY

这种结构确实自成一派。

A Theoretical and Empirical Analysis of Program Spectra Diagnosability

来源:想的

引用:

@article{perez_theoretical_2019,
title = {A {Theoretical} and {Empirical} {Analysis} of {Program} {Spectra} {Diagnosability}},
journal = {IEEE Transactions on Software Engineering},
author = {Perez, Alexandre and Abreu, Rui and Van Deursen, Arie},
year = {2019},
file = {Snapshot:D:\software\zotero\pdf-download-path\storage\CPKNS6QM\8627980.html:text/html}
}

基本内容:
Current metrics for assessing the adequacy of a test-suite plainly focus on the number of components (be it lines, branches, paths) covered by the suite, but do not explicitly check how the tests actually exercise these components and whether they provide enough information so that spectrum-based fault localization techniques can perform accurate fault isolation. We propose a metric, called DDU, aimed at complementing adequacy measurements by quantifying a test-suite’s diagnosability, i.e., the effectiveness of applying spectrum-based fault localization to pinpoint faults in the code in the event of test failures. Our aim is to increase the value generated by creating thorough test-suites, so they are not only regarded as error detection mechanisms but also as effective diagnostic aids that help widely-used fault-localization techniques to accurately pinpoint the location of bugs in the system. We have performed a topology-based simulation of thousands of spectra and have found that DDU can effectively establish an upper bound on the effort to diagnose faults. Furthermore, our empirical experiments using the Defects4J dataset show that optimizing a test suite with respect to DDU yields a 34% gain in spectrum-based fault localization report accuracy when compared to the standard branch-coverage metric.

有意思。
1)针对的是测试用例的metric(充分性度量)
2)提到了upper bound,虽然这个abstract我没看懂。但是这个有意思
3)DDU还在Defects4J上做了测试,yields a 34% gain in SFL report accuracy 这个厉害。

在这里插入图片描述这个simulator,让我想到了之前的工作。。。

大牛写文章,真的不一样。。。
有时间得好好揣摩下这里面的各种公式。

An empirical study on TensorFlow program bugs

来源:想的
引用:
@inproceedings{zhang_empirical_2018,
title = {An empirical study on {TensorFlow} program bugs},
booktitle = {Proceedings of the 27th {ACM} {SIGSOFT} {International} {Symposium} on {Software} {Testing} and {Analysis}},
publisher = {ACM},
author = {Zhang, Yuhao and Chen, Yifan and Cheung, Shing-Chi and Xiong, Yingfei and Zhang, Lu},
year = {2018},
pages = {129–140},
file = {Full Text:D:\software\zotero\pdf-download-path\storage\M65CI8ZU\Zhang 等。 - 2018 - An empirical study on TensorFlow program bugs.pdf:application/pdf;Snapshot:D:\software\zotero\pdf-download-path\storage\5Z4H6JLI\citation.html:text/html}
}

内容:
Deep learning applications become increasingly popular in impor- tant domains such as self-driving systems and facial identity sys- tems. Defective deep learning applications may lead to catastrophic consequences. Although recent research efforts were made on test- ing and debugging deep learning applications, the characteristics of deep learning defects have never been studied.

这个点,很妙。

好词好句:

  • have been proposed to facilitate programming of such applications.
  • applications differs significantly from that of traditional applications
  • The development of DL applications often faces tasks that are seldom encountered in developing their traditional counterparts, e.g., configuring
  • As DL is increasingly adopted for mission-critical applications
  • defective DL applications can lead to catastrophic consequences
  • Despite these efforts, the characteristics of defects in DL applications have never been systematically studied. In particular, it is still unclear what new challenges the paradigm shift from traditional program languages to DL languages bring to fault detection and localization.

这是高手。。。写的太好了

  • To ease presentation, we refer to the defects in TF programs as bugs. We
    (这表述真的太专业了。。。)
  • Our study has led to multiple findings. In particular, we identify
    four types of symptoms, seven types of root causes, five challenges in detection and fault localization, and five strategies that the TF users have adopted to address the challenges.
    (这种实证真的很牛)

组织方式:
The rest ofthe paper is organized as follows. In Section 2, we pro-
vide a background ofprogramming over the TensorFlow framework. In Section 3, we propose three research questions. In Section 4, we present howwe collected our data. In Section 5, 6, and 7, we answer these three research questions respectively

框架:
3 RESEARCH QUESTIONS
4 DATA COLLECTION
5 RQ1: SYMPTOMS AND ROOT CAUSES
6 RQ2
7 RQ3
8 THREATS TO VALIDITY

  • First, our study involves manual inspections on bugs. These subjec- tive steps can be biased due to our inference of the code’s intention in the lack of documentation. In order to reduce this threat, two authors analyzed the bugs separately and discussed inconsistent issues until an agreement was reached. 很有意思,很值得学习。

学到了。。。

Two groups of people can benefit from this study. For TF users,
we summarized five strategies used by other TF users to detect and debug the bugs in TF programs. For software engineering researchers, we pointed out five new challenges which call for more research efforts. Our classification of causes and symptoms offers both TF users and software engineering researchers a better understanding of deep learning program bugs.

(字字珠玑。多学多读)

An Empirical Study on Real Bug Fixes

来源:联想

引用:
@inproceedings{zhong_empirical_2015,
title = {An empirical study on real bug fixes},
booktitle = {Proceedings of the 37th {International} {Conference} on {Software} {Engineering}-{Volume} 1},
publisher = {IEEE Press},
author = {Zhong, Hao and Su, Zhendong},
year = {2015},
pages = {913–923},
file = {Full Text:D:\software\zotero\pdf-download-path\storage\SMA23DDF\Zhong 和 Su - 2015 - An empirical study on real bug fixes.pdf:application/pdf}
}

这个调查的覆盖面有点广,而且结论很多,很杂。
很有意思

II. METHODOLOGY (主要讲数据集的收集制作)
A. Dataset
B. Research Questions

III. EMPIRICAL RESULTS
A. RQ1: Fault Distribution
B-F (全是RQs)
G. Threats to Validity

IV. DISCUSSIONS AND FUTURE WORK

LogTracker: Learning Log Revision Behaviors Proactively from Software Evolution History

来源:联想
引用:

内容:
For taking the first step towards solving the second problem, this paper is inspired by code clones and assumes that logging code with similar context is pervasive in software and deserves similar modifications. To verify our as- sumptions, we conduct an empirical study on eight open-source projects.

这个挺有意义的。

Fine-grained and accurate source code differencing

来源:想看看GumTree这个工具

引用:
@inproceedings{falleri_fine-grained_2014,
title = {Fine-grained and accurate source code differencing},
booktitle = {Proceedings of the 29th {ACM}/{IEEE} international conference on {Automated} software engineering},
publisher = {ACM},
author = {Falleri, Jean-Rémy and Morandat, Floréal and Blanc, Xavier and Martinez, Matias and Monperrus, Martin},
year = {2014},
pages = {313–324},
file = {Snapshot:D:\software\zotero\pdf-download-path\storage\P8KLC9H5\citation.html:text/html}
}

内容:
At the heart of software evolution is a sequence of edit actions, called an edit script, made to a source code file. Since software systems are stored version by version, the edit script has to be computed from these versions, which is known as a complex task. Existing approaches usually compute edit scripts at the text granularity with only add line and delete line actions. However, inferring syntactic changes from such an edit script is hard. Since moving code is a frequent action performed when editing code, it should also be taken into account. In this paper, we tackle these issues by introducing an algorithm computing edit scripts at the abstract syntax tree granularity including move actions. Our objective is to compute edit scripts that are short and close to the original developer intent. Our algorithm is implemented in a freely-available and extensible tool that has been intensively validated.

原来是一个计算、展示代码差分的工具。

小结

今天看到朋友圈一篇文章,说如何自我突破的。
其中提到的重要因素:兴趣
细细想来,果真如此。

没有兴趣,很多事情都做不成。

本文来自互联网用户投稿,该文观点仅代表作者本人,不代表本站立场。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如若转载,请注明出处:http://www.rhkb.cn/news/66272.html

如若内容造成侵权/违法违规/事实不符,请联系长河编程网进行投诉反馈email:809451989@qq.com,一经查实,立即删除!

相关文章

隐私保护论文题目汇总(一定要保持更新)

Motivation 既然放养,只能自救,大家都是我的导师。 研究方向争取不乱串。隐私保护。 2022.5.26 1 Blockchain Empowered Asynchronous Federated Learning for Secure Data Sharing in Internet of Vehicles (2020 IEEE Trans on vehicul…

论文学习笔记(二):面对多步攻击的网络安全态势评估

文章目录 1. 引言2. 网络安全态势评估基础2.1 基本术语2.2 网络安全态势评估流程 3. 实时攻击阶段识别3.1 攻击场景聚类3.2 实时攻击阶段识别算法3.3 攻击阶段识别算法的改进 4 网络安全态势量化分析4.1 攻击安全概率4.2 攻击阶段实现概率4.3 网络安全态势值 5 实验结果及分析5…

个人信息安全事件应急处理和报告

声明 本文是学习GB-T 35273-2020 信息安全技术 个人信息安全规范. 而整理的学习笔记,分享出来希望更多人受益,如果存在侵权请及时联系我们 个人信息安全事件处置 个人信息安全事件应急处置和报告 对个人信息控制者的要求包括: 应制定个人信息安全事件应急预案&…

论文总结:云安全研究方向及进展综述

目录 1、云安全在信息安全领域所处位置 2、云计算环境面临的威胁和挑战 2.1 云安全发展史 2.2 云计算安全与传统计算安全区别[5] 2.3 从顶层框架的角度看云安全研究目标 3、研究进展和解决方案 3.1 虚拟化、数据、应用安全[6] 3.2 系统安全、网络安全、数据安全[7] 3.3…

信息系统安全实验之文件上传漏洞导致主页篡改实验

一、实验目的 1.了解文件上传漏洞的原理和攻击方式。 2.在学习该漏洞的出现原因的过程中了解该漏洞的防范和加固方式。 二、实验环境 1.操作系统:Windows 7(虚拟机环境)。 2.工具:phpStudy、Burp Suite、中国蚁剑、Firefox浏…

使用崩溃服务,获取不到崩溃报告怎么办

华为AGC推出的崩溃服务,零代码集成,只需要添加SDK即可。有时可能集成了SDK,在AGC页面获取不到崩溃报告,总结了一下可以排查以下几点: 1、首先确认下端侧有没有上报 执行“adb shell setprop log.tag.AGC_LOG VERBOSE…

说说计算这事儿:从开关到人工智能

目录 一 前言 二 计算历史 三 计算探秘 四 算力优化 五 未来展望 一 前言 计算本身其实是一个比较抽象的词,或者说比较笼统。很多场景都可能用到计算这个词,因此具体的含义就需要根据上下文来确定。今天我们讨论的计算,是比较狭义的计算…

稚晖君,被百度投了!估值被曝已超独角兽

推荐阅读:“程序员交友网站” SO 突然裁员 10%,网友:ChatGPT 出来后就不咋用了 衡宇 发自 凹非寺量子位 | 公众号 QbitAI “华为天才少年”稚晖君创业项目,刚被百度风投投了! 量子位获悉,稚晖君创业项目智元…

充能书单|618,买什么都不如买知识!

前言 “IT有得聊”是机械工业出版社旗下IT专业资讯和服务平台,致力于帮助读者在广义的IT领域里,掌握更专业、更实用的知识与技能,快速提升职场竞争力。 点击蓝色微信名可快速关注我们。 一年一度的618又到啦!今年的618就不要乱买…

华为鸿蒙os有微信吗,华为“鸿蒙OS”合作的多个软件 没有微信你还会用吗

花火网讯 11月12日消息,华为“鸿蒙OS”合作了很多个软件,但是里面竟然没有微信,你还会选择华为鸿蒙OS吗? 手机如今大家都离不开它,并且如今的手机给了我们很多的方便,也正因为如此,现在的人越来…

鸿蒙取得成功后,互联网企业牵头研发操作系统挑战安卓

在鸿蒙系统突破3亿用户数之后,日前传出消息指国内互联网巨头腾讯与酷派合作再研发手机操作系统,此举或许有望吸引国内诸多手机企业参与,将为国产手机操作系统打破安卓的垄断再添一份力。 华为可以说是被迫上鸿蒙系统的吧,2019年的…

汇聚开发者星星之火,华为鸿蒙系统有希望成为国产之光?

作者 | 雷架 来源 | 爱笑的架构师(ID:DancingOnYourCode) 头图 | CSDN 下载自东方IC 鸿蒙系统2.0的发布给国人带来极大的振奋,虽然有一部分人不断唱衰,觉得是大家被爱国情怀所左右,但大部分人的激动其实原…

华为背水一战,未来所有终端将仅用鸿蒙系统

有知名大V透露华为将在3月份发布最后一个基于安卓系统开发的EMUI11.1系统,此后将完全采用鸿蒙系统,这显示出它在面临巨大困难之后作出的抉择。 华为此前研发的EMUI系统说到底还是安卓系统,EMUI主要用于国内的手机上,而在海外市场则…

鸿蒙系统能用在高通上吗,其它厂商也能用,华为做出重要决定,鸿蒙OS完全开源并适配高通...

原标题:其它厂商也能用,华为做出重要决定,鸿蒙OS完全开源并适配高通 其它厂商也能用,华为做出重要决定,鸿蒙OS完全开源并适配高通 这可能是大多数国内消费者最想看到的结果吧,华为做出重要决定,…

统信软件华为 | 携手同行,共建产业新生态,共创行业新价值

9月23日至26日,华为全联接大会2020在上海世博中心成功举行,统信软件作为华为长期战略合作伙伴受邀出席。 大会期间,统信软件参与了多场线上线下专题演讲并展示了与华为合作的最新成果。 携手共建软硬件创新生态 9月23日,统信软件…

鸿蒙系统有hms推送机制,华为推送HMS服务,依靠鸿蒙OS,或将改变手机行业格局...

原标题:华为推送HMS服务,依靠鸿蒙OS,或将改变手机行业格局 谷歌在去年5月的时候停止授权GMS服务,自此,华为手机销量出现了极速下跌,而华为也不敢如此,并且在之后的不就开始了自己的自救行动。 就…

华为鸿蒙系统开源以建立生态,然同业竞争关系让它恐难获得支持

华为正式发布了鸿蒙系统,在它的PPT介绍中,鸿蒙系统在时延、流畅性等方面俱有优势,主要的弱点在于生态方面,这也是以往众多操作系统失败的缘由,为解决鸿蒙系统的生态问题,鸿蒙系统将采用开源的方式发展&…

HarmonyOS新能力让数据多端协同更便捷,数据跨端迁移更高效

作者:yijian,终端OS分布式文件系统专家;gongashi,终端OS分布式数据管理专家 HarmonyOS作为分布式操作系统,其分布式数据管理能力非常重要。我们也一直围绕持续为开发者带来全局“一份”数据的开发体验的目标&#xff0…

滋灌中小企业,分销伙伴和华为来做“送水人”

最近有个段子:第一批靠生成式AI赚大钱的人,既不是研发人员,也不是国内大厂,而是卖课的。 大家笑谈,每一轮新技术的掘金之路,最先致富的都是送水、卖铲子的。 这其实隐藏了一个信息技术产业的普遍规律&#…

除了新发布鸿蒙系统,华为还在HMS生态上下功夫

近日,华为举办鸿蒙系统(HarmonyOS)发布会,一时之间「鸿蒙手机来了」话题迅速占领热搜榜。作为一个国产移动操作系统,它被寄予了无数国人的期待、支持。 想要真正打造操作系统,关键点在于能否形成软件生态。鸿蒙系统背后&#xff0…