CREDAL: Towards Locating a Memory Corruption Vulnerability with Your Core Dump
暂无分享,去创建一个
Peng Liu | Jun Xu | Pei Wang | Xinyu Xing | Ping Chen | Dongliang Mu
[1] Susan Horwitz,et al. Better Debugging via Output Tracing and Callstack-Sensitive Slicing , 2010, IEEE Transactions on Software Engineering.
[2] Sudheendra Hangal,et al. Tracking down software bugs using automatic anomaly detection , 2002, ICSE '02.
[3] Nachiappan Nagappan,et al. Crash graphs: An aggregated view of multiple crashes to improve crash triage , 2011, 2011 IEEE/IFIP 41st International Conference on Dependable Systems & Networks (DSN).
[4] Milo M. K. Martin,et al. SoftBound: highly compatible and complete spatial memory safety for c , 2009, PLDI '09.
[5] Dongmei Zhang,et al. ReBucket: A method for clustering duplicate crash reports based on call stack similarity , 2012, 2012 34th International Conference on Software Engineering (ICSE).
[6] Ben Liblit,et al. Cores, Debugging, and Coverage , 2015 .
[7] David A. Wagner,et al. Dynamic Test Generation to Find Integer Bugs in x86 Binary Linux Programs , 2009, USENIX Security Symposium.
[8] A. Zeller. Isolating cause-effect chains from computer programs , 2002, SIGSOFT '02/FSE-10.
[9] Galen C. Hunt,et al. Debugging in the (very) large: ten years of implementation and experience , 2009, SOSP '09.
[10] Ben Liblit,et al. Dynamic heap type inference for program understanding and debugging , 2007, POPL '07.
[11] Manu Sridharan,et al. PSE: explaining program failures via postmortem static analysis , 2004, SIGSOFT '04/FSE-12.
[12] Gregor Kiczales,et al. Interacting with dead objects , 2013, OOPSLA.
[13] George Candea,et al. Code-pointer integrity , 2014, OSDI.
[14] A Pnueli,et al. Two Approaches to Interprocedural Data Flow Analysis , 2018 .
[15] Robert E. Strom,et al. Typestate: A programming language concept for enhancing software reliability , 1986, IEEE Transactions on Software Engineering.
[16] Ben Liblit,et al. CSIclipse: presenting crash analysis data to developers , 2015, ETX.
[17] H. Cleve,et al. Locating causes of program failures , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..
[18] Rahul Premraj,et al. Do stack traces help developers fix bugs? , 2010, 2010 7th IEEE Working Conference on Mining Software Repositories (MSR 2010).
[19] Peter Ohmann. Making your crashes work for you (doctoral symposium) , 2015, ISSTA.
[20] Ding Yuan,et al. Improving Software Diagnosability via Log Enhancement , 2012, TOCS.
[21] James R. Larus,et al. The use of program profiling for software maintenance with applications to the year 2000 problem , 1997, ESEC '97/FSE-5.
[22] Ding Yuan,et al. SherLog: error diagnosis by connecting clues from run-time logs , 2010, ASPLOS XV.
[23] Derek Bruening,et al. AddressSanitizer: A Fast Address Sanity Checker , 2012, USENIX Annual Technical Conference.
[24] Daniel M. Yellin,et al. Extending Typestate Checking Using Conditional Liveness Analysis , 1993, IEEE Trans. Software Eng..
[25] Alex Aiken,et al. Building a Better Backtrace: Techniques for Postmortem Program Analysis , 2002 .
[26] Yanick Fratantonio,et al. RETracer: Triaging Crashes by Reverse Execution from Partial Memory Dumps , 2016, 2016 IEEE/ACM 38th International Conference on Software Engineering (ICSE).
[27] Rongxin Wu,et al. CrashLocator: locating crashing faults based on crash stacks , 2014, ISSTA 2014.
[28] Vikram S. Adve,et al. Using likely invariants for automated software fault localization , 2013, ASPLOS '13.
[29] Steven P. Reiss,et al. Fault localization with nearest neighbor queries , 2003, 18th IEEE International Conference on Automated Software Engineering, 2003. Proceedings..