DSpace at VNU: FixBag: A fixpoint calculator for quantified bag constraints

778 1.2K 0
DSpace at VNU: FixBag: A fixpoint calculator for quantified bag constraints

Đang tải... (xem toàn văn)

Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống

Thông tin tài liệu

DSpace at VNU: FixBag: A fixpoint calculator for quantified bag constraints tài liệu, giáo án, bài giảng , luận văn, luậ...

Lecture Notes in Computer Science Commenced Publication in 1973 Founding and Former Series Editors: Gerhard Goos, Juris Hartmanis, and Jan van Leeuwen Editorial Board David Hutchison Lancaster University, UK Takeo Kanade Carnegie Mellon University, Pittsburgh, PA, USA Josef Kittler University of Surrey, Guildford, UK Jon M Kleinberg Cornell University, Ithaca, NY, USA Alfred Kobsa University of California, Irvine, CA, USA Friedemann Mattern ETH Zurich, Switzerland John C Mitchell Stanford University, CA, USA Moni Naor Weizmann Institute of Science, Rehovot, Israel Oscar Nierstrasz University of Bern, Switzerland C Pandu Rangan Indian Institute of Technology, Madras, India Bernhard Steffen TU Dortmund University, Germany Madhu Sudan Microsoft Research, Cambridge, MA, USA Demetri Terzopoulos University of California, Los Angeles, CA, USA Doug Tygar University of California, Berkeley, CA, USA Gerhard Weikum Max Planck Institute for Informatics, Saarbruecken, Germany 6806 Ganesh Gopalakrishnan Shaz Qadeer (Eds.) Computer Aided Verification 23rd International Conference, CAV 2011 Snowbird, UT, USA, July 14-20, 2011 Proceedings 13 Volume Editors Ganesh Gopalakrishnan University of Utah School of Computing 50 South Central Campus Dr Salt Lake City, UT 84112-9205, USA E-mail: ganesh@cs.utah.edu Shaz Qadeer Microsoft Research One Microsoft Way Redmond, WA 98052, USA E-mail: qadeer@microsoft.com ISSN 0302-9743 e-ISSN 1611-3349 e-ISBN 978-3-642-22110-1 ISBN 978-3-642-22109-5 DOI 10.1007/978-3-642-22110-1 Springer Heidelberg Dordrecht London New York Library of Congress Control Number: 2011930052 CR Subject Classification (1998): F.3, D.2, D.3, D.2.4, F.4.1, C.2 LNCS Sublibrary: SL – Theoretical Computer Science and General Issues © Springer-Verlag Berlin Heidelberg 2011 This work is subject to copyright All rights are reserved, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, re-use of illustrations, recitation, broadcasting, reproduction on microfilms or in any other way, and storage in data banks Duplication of this publication or parts thereof is permitted only under the provisions of the German Copyright Law of September 9, 1965, in its current version, and permission for use must always be obtained from Springer Violations are liable to prosecution under the German Copyright Law The use of general descriptive names, registered names, trademarks, etc in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use Typesetting: Camera-ready by author, data conversion by Scientific Publishing Services, Chennai, India Printed on acid-free paper Springer is part of Springer Science+Business Media (www.springer.com) Preface The International Conference on Computer-Aided Verification (CAV) is dedicated to the advancement of the theory and practice of computer-aided formal analysis methods for hardware and software systems Its scope ranges from theoretical results to concrete applications, with an emphasis on practical verification tools and the underlying algorithms and techniques This volume contains the proceedings of the 23rd edition of this conference held in Snowbird, Utah, USA, during July 14–20, 2011 The conference included two workshop days, a tutorial day, and four days for the main program At CAV 2009, Bob Kurshan approached us with the idea of holding CAV 2011 in Salt Lake City Encouraged by the enthusiastic support from late Amir Pnueli, we had little hesitation in agreeing to Bob’s proposal While the initial proposal was to organize the conference on the campus of the University of Utah, we eventually decided to hold it at the Snowbird resort near Salt Lake City Our decision was motivated by the dual desire to showcase the abundant natural beauty of Utah and to provide a collegial atmosphere similar to a Dagstuhl workshop We are happy to report that CAV is thriving, as evidenced by the large number of submissions We received 161 submissions and selected 35 regular and 20 tool papers We appreciate the diligence of our Program Committee and our external reviewers due to which all (except two) papers received at least four reviews A big thank you to all our reviewers! The conference was preceded by the eight affiliated workshops: – The 4th International Workshop on Numerical Software Verification (NSV 2011), Thursday, 7/14 – 10th International Workshop on Parallel and Distributed Methods in Verifications (PDMC 2011), Thursday, 7/14 – The 4th International Workshop on Exploiting Concurrency Efficiently and Correctly (EC2 2011), 7/14-7/15 – Frontiers in Analog Circuit Synthesis and Verification (FAC 2011), 7/14-7/15 – International Workshop on Satisfiability Modulo Theories, including SMTCOMP (SMT 2011), 7/14-7/15 – 18th International SPIN Workshop on Model Checking of Software (SPIN 2011), 7/14-7/15 – Formal Methods for Robotics and Automation (FM-R 2011), 7/15 – Practical Synthesis for Concurrent Systems (PSY 2011), 7/15 In addition to the presentations for the accepted papers, the conference also featured four invited talks and four invited tutorials – Invited talks: • Andy Chou (Coverity Inc.): “Static Analysis Tools in Industry: Notes from the Front Line” VI Preface • Vigyan Singhal and Prashant Aggarwal (Oski Technology): “Using Coverage to Deploy Formal Verification in a Simulation World” • Vikram Adve (University of Illinois at Urbana-Champaign): “Parallel Programming Should Be and Can Be Deterministic-by-default” • Rolf Ernst (TU Braunschweig): “Formal Performance Analysis in Automotive Systems Design: A Rocky Ride to New Grounds” – Invited tutorials: • Shuvendu Lahiri (Microsoft Research): “SMT-Based Modular Analysis of Sequential Systems Code” • Vijay Ganesh (Massachussetts Institute of Technology): “HAMPI: A String Solver for Testing, Analysis and Vulnerability Detection” • Ranjit Jhala (University of California at San Diego): “Using Types for Software Verification” • Andre Platzer (Carnegie Mellon University): “Logic and Compositional Verification of Hybrid Systems” A big thank you to all our invited speakers! We thank the members of the CAV Steering Committee —Michael Gordon, Orna Grumberg, Bob Kurshan, and Ken McMillan— for their timely advice on various organizational matters Neha Rungta, our Workshop Chair, smoothly handled the organization of the workshops Eric Mercer, our Local Arrangements Chair, set up the registration portal at Brigham Young University Sandip Ray, our Publicity Chair, helped publicize CAV 2011 We thank Aarti Gupta, past CAV Chair, for her help and advice in running the conference and maintaining its budget We thank Geof Sawaya for maintaining the CAV 2011 website We are grateful to Wendy Adamson for arranging the beautiful Cliff Lodge facility at an affordable price and really making the budget work in our favor We thank Alfred Hofmann of Springer for publishing the paper and USB proceedings for CAV 2011 We thank Andrei Voronkov and his team for offering us EasyChair which has proven invaluable at every juncture in conducting the work of CAV We thank the office staff of the School of Computing, University of Utah, especially Karen Feinauer and Chris Coleman, for allowing us to use the school resources for managing CAV activities We are especially grateful to our corporate sponsors —Microsoft Research, Coverity, Google, NEC Research, Jasper, IBM, Intel, Fujitsu, and Nvidia— for their donations We are also grateful to Judith Bishop and Wolfram Schulte of Microsoft Research for their substantial financial backing of CAV We also thank Lenore Zuck, Nina Amla, and Sol Greenspan who helped with obtaining an NSF travel award CAV 2012 will be held in Berkeley, California April 2011 Ganesh Gopalakrishnan Shaz Qadeer Organization Program Committee Azadeh Farzan Jasmin Fisher Cormac Flanagan Steven German Dimitra Giannakopoulou Ganesh Gopalakrishnan Susanne Graf Keijo Heljanko William Hung Franjo Ivancic Joost-Pieter Katoen Stefan Kowalewski Daniel Kroening Orna Kupferman Robert P Kurshan Akash Lal Kim G Larsen Ken Mcmillan Madan Musuvathi Michael Norrish Madhusudan Parthasarathy Shaz Qadeer John Regehr Andrey Rybalchenko Sriram Sankaranarayanan Roberto Sebastiani Sanjit A Seshia Ofer Strichman Murali Talupur Serdar Tasiran Ashish Tiwari Tayssir Touili Viktor Vafeiadis Bow-Yaw Wang University of Toronto, Canada Microsoft Research, Cambridge, UK University of California at Santa Cruz, USA IBM Yorktown Heights, NY RIACS/NASA Ames, USA University of Utah, USA Universit´e Joseph Fourier, CNRS, VERIMAG, France Helsinki University of Technology, Finland Synopsys Inc., USA NEC Labs America, USA RWTH Aachen, Germany RWTH Aachen, Germany Oxford University, UK Hebrew University, Israel Cadence Design Systems, USA Microsoft Research, Bangalore, India Aalborg University, Denmark Microsoft Research, Redmond, USA Microsoft Research, Redmond, USA NICTA, Australia University of Illinois at Urbana-Champaign, USA Microsoft Research, Redmond, USA University of Utah, USA TU Munich, Germany University of Colorado at Boulder, USA University of Trento, Italy University of California at Berkeley, USA Technion, Israel Intel, Santa Clara, USA Koc University, Turkey SRI International, Menlo Park, USA LIAFA, CNRS, France and Universit´e Paris Diderot MPI-SWS, Germany Academia Sinica, Taiwan VIII Organization Additional Reviewers A Abraham, Erika Ait Mohamed, Otmane Alglave, Jade Andres, Miguel E Asarin, Eugene Atig, Faouzi B Baier, Christel Balakrishnan, Gogul Barakat, Kamal Batty, Mark Bauer, Andreas Bell, Christian Bensalem, Saddek Berdine, Josh Bhattacharya, Ritwik Biallas, Sebastian Biere, Armin Bingham, Jesse Boker, Udi Bonakdarpour, Borzoo Bouajjani, Ahmed Bozzano, Marco Brady, Bryan Brauer, Jă org Brihaye, Thomas Bruttomesso, Roberto Buchholz, Peter Burckhardt, Sebastian C Cabodi, Gianpiero Cardelli, Luca Case, Michael Chan, Yang Chaudhuri, Swarat Chechik, Marsha Chen, Taolue Chen, Xiaofang Chen, Yang Chen, Yu-Fang Cook, Byron D D’Argenio, Pedro R D’Silva, Vijay Dang, Thao David, Alexandre De Moura, Leonardo De Paula, Flavio M De Rougemont, Michel Distefano, Dino Donaldson, Alastair Donz´e, Alexandre Doyen, Laurent Dragoi, Cezara Duan, Jianjun Dubrovin, Jori Durairaj, Vijay Dutertre, Bruno E Een, Niklas Elenbogen, Dima Elmas, Tayfun Emmer, Moshe Emmi, Michael Enea, Constantin F Fahrenberg, Uli Ferrante, Alessandro Forejt, Vojtech Franke, Dominik Freund, Stephen G Gan, Xiang Ganai, Malay Ganesh, Vijay Garg, Pranav Garnier, Florent Organization Ghorbal, Khalil Gimbert, Hugo Girard, Antoine Godefroid, Patrice Gotsman, Alexey Griggio, Alberto Groce, Alex Grundy, Jim Gueckel, Dominique Gupta, Ashutosh Gurfinkel, Arie H Haemmerl´e, R´emy Haensch, Paul Haller, Leopold Hartmanns, Arnd He, Fei He, Nannan Heinen, Jonathan Heizmann, Matthias Holcomb, Daniel Huang, Chung-Yang Ric Humphrey, Alan J Jalbert, Nicholas Janhunen, Tomi Jansen, Christina Janssen, Geert Jha, Susmit Jhala, Ranjit Jiang, Jie-Hong Roland Jin, Hoonsang Jin, Naiyong Jobstmann, Barbara Jones, Robert Junttila, Tommi Jă urjens, Jan K Kahlon, Vineet Kaiser, Alexander Kamin, Volker Kim, Hyondeuk Kincaid, Zachary Kindermann, Roland King, Andy Kishinevsky, Michael Kodakara, Sreekumar Kotker, Jonathan Krepska, Elzbieta Krstic, Sava Kwiatkowska, Marta Kă ahkă onen, Kari Kă opf, Boris L La Torre, Salvatore Lahiri, Shuvendu Launiainen, Tuomas Leroux, Jerome Levhari, Yossi Lewis, Matt Li, Guodong Li, Jian-Qi Li, Wenchao Logozzo, Francesco Lvov, Alexey M Mador-Haim, Sela Maeda, Naoto Majumdar, Rupak Maler, Oded Malkis, Alexander Maoz, Shahar Mardare, Radu Mateescu, Maria Mayr, Richard Mereacre, Alexandru Merschen, Daniel Might, Matthew Miner, Paul Mishchenko, Alan Mitra, Sayan Mogavero, Fabio Mover, Sergio Murano, Aniello IX X Organization N Nain, Sumit Napoli, Margherita Narasamdya, Iman Nickovic, Dejan Nimal, Vincent Noll, Thomas Norman, Gethin Nuzzo, Pierluigi Nyman, Ulrik P Palmer, Robert Pandav, Sudhindra Parente, Mimmo Parker, David Parlato, Gennaro Pedersen, Mikkel L Pek, Edgar Peled, Doron Pike, Lee Piskac, Ruzica Piterman, Nir Platzer, Andre Popeea, Corneliu Q Qian, Kairong Qiang, Katherine Qiu, Xiaokang Quesel, Jan-David Quinton, Sophie Rogalewicz, Adam Rozanov, Mirron Rozier, Kristin Yvonne Rungta, Neha Ryvchin, Vadim S Sa’Ar, Yaniv Sahoo, Debashis Sangnier, Arnaud Sanner, Scott Saxena, Prateek Schewe, Sven Schlich, Bastian Schuppan, Viktor Segerlind, Nathan Sen, Koushik Sepp, Alexander Serbanuta, Traian Sevcik, Jaroslav Sezgin, Ali Sharma, Subodh Sheinvald, Sarai Sighireanu, Mihaela Sinha, Nishant Spalazzi, Luca Srba, Jiri Srivastava, Saurabh Stefanescu, Alin Steffen, Bernhard Stoelinga, Marielle Stoller, Scott Stursberg, Olaf Szubzda, Grzegorz R T Rajan, Ajitha Ravi, Kavita Reinbacher, Thomas Rezine, Ahmed Ridgeway, Jeremy Rinetzky, Noam Rintanen, Jussi Rival, Xavier Tautschnig, Michael Thrane, Claus Tiu, Alwen Tonetta, Stefano Tsai, Ming-Hsien Tsay, Yih-Kuen Tuerk, Thomas Practical, Low-Effort Equivalence Verification of Real Code 681 terminated with an out-of-bounds read when environ is NULL (e.g., after a call to the function clearenv), while the new code (right) exited gracefully: : char **ep = environ; : while (*ep != NULL) { } (a) unsetenv: uClibc 0.9.30.3 4.3 : char **ep = environ; : if (ep) while (*ep != NULL) { } (b) unsetenv: uClibc 0.9.31 Checking the Checker: Finding Bugs in UC-KLEE and LLVM A standard caveat in verification papers is that their claims are contingent on the correctness of the verifier and underlying compiler One of our contributions is the realization that one can detect errors in both by simply attempting to prove the equivalence of identical code, thus turning the verification system on itself Finding compiler optimizer bugs We check that an optimizer has correctly transformed a program path by compiling the same routine both with and without optimization and cross checking the results With the usual caveats, if any possible value exists that would cause the path to give different results, uc-klee will detect it If there is no such value, it has verified that the optimizer worked correctly on the checked path If it terminates, it has shown that the optimizer transformed the entire routine correctly Any discrepancies it finds are due to either compiler bugs or the routine depending on unspecified behavior (e.g., function evaluation order between sequence points) Because the library code we checked intends to be portable, even use of unspecified compiler behavior almost certainly constitutes an error We compared all 622 procedures in uClibc 0.9.31, compiled with no optimization (-O0) versus high optimization (-O3) This check uncovered at least one bug in llvm 2.6’s optimizer but did not expose its root cause For memmem, uc-klee reported a set of concrete inputs where the unoptimized code returned an offset within haystack (the correct result), while the optimized code returned NULL, indicating that needle was not found in haystack We confirmed this bug with a small program Since llvm is a mature, production compiler, the fact that we immediately found bugs in this simple way is a strong result We found a total of 70 differences, but because of time constraints could not determine whether they were due to this bug or others Future work will be necessary to test optimization levels between these two extremes and attempt to automatically find a minimal set of optimization passes that yield an observable difference Finding UC-KLEE bugs In general, tool developers can detect verifier bugs by simply cross checking a routine against another identical copy of itself (i.e., compiled at the same optimization level) This check has been a cornerstone of debugging uc-klee—it often turned up tricky errors after development pushes The uc-klee bugs we found fell into two main categories: (1) unwanted nondeterminism in uc-klee and its environmental models, which makes it hard to replay paths or get consistent results, and (2) bugs in our initial pointer tracking approach In fact, as a direct result of the tricky cases cross checking exposed in this pointer tracking implementation, we threw it away and instead designed the much simpler and robust method in Section 3.1 682 4.4 D.A Ramos and D.R Engler Results summary Figure summarizes the results presented in this section The “klee Limitations” row describes procedures that resulted in incomplete testing due to limitations in the underlying klee tool: inline assembly (141 procedures), external calls with symbolic arguments (206), and unresolved external calls (17) “uc-klee Limitations” are cases where the tool failed to lazily allocate objects either because the required size of the object exceeded our specified maximum of 2KB (20 procedures) or uc-klee was unable to allocate an object whose address satisfied the path constraints (117 procedures) Note that limitations resulted in individual paths being terminated As a result, certain procedures encountered a variety of limitations on different paths In particular, a procedure deemed “klee limited” may have also encountered uc-klee limitations, although the converse is not true Procedures Checked Procedures Verified Differences Detected No Differences (timeout) klee Limitations uc-klee Limitations 100% Coverage Mean Coverage Median Coverage Newlib/ uClibc 143 66 57 15 59 72.2% 90.1% uClibc Versions 203 84 20 30 56 13 105 80.7% 100.0% llvm Optimizer 622 335 70 85 94 38 367 85.6% 100.0% uc-klee Self-check 622 335 12 91 147 37 375 85.6% 100.0% Fig Breakdown of procedures checked in each experiment Related Work This paper builds on the many recent research projects in symbolic execution, such as [2,3,12,16,22], as well as several pieces of our past work About a decade ago, we showed how to avoid the need for manual specification by cross checking multiple implementations in the context of static bug finding [9], an idea we later used with symbolic execution [2,3] This latter work only handled complete applications or routines run on manually constructed symbolic input; this paper shows how to easily check code fragments with unbound inputs and how to use cross checking to find bugs in the checking infrastructure itself This paper is related to under-constrained execution [8], but modified to support the cross checking context, where many of the tricky issues are elided Many previous approaches to software checking have been specification based, requiring extensive work on the part of the user One example is the use of model checking to find bugs in both the design and the implementation of software [1,4, 5,11,13,14], which requires manually building test harnesses A second example is recent verification work that checks code manipulating complex data structures against manually constructed specifications [6,7,10,18] While both can exploit their specifications to reduce the state space, they require far more user effort than uc-klee Similar work has attempted to cross check largely identical code by using over-approximation to filter out unchanged portions of Java code [20] While Practical, Low-Effort Equivalence Verification of Real Code 683 their technique is sound with respect to verification, a consequence of overapproximation is that reported differences may not concretely affect the output In contrast, uc-klee generates test cases that supply concrete inputs to expose behavioral differences in the code Earlier work in cross checking has focused on combinational circuits in hardware [4,17,19] While an important milestone, hardware verification is simpler than general purpose software equivalence checking, which includes loops, complex pointer relationships, and other difficult constructs Smith and Dill [23] recently verified the correctness of real-world block cipher implementations Their work exploits the key properties that block ciphers have fixed input sizes and loop iterations, enabling full loop unrolling They developed several constraint optimizations that we hope to adapt for cross-checking generalpurpose code Conclusion We have presented uc-klee, a tool that often makes cross checking two implementations of the same interface easier than writing even a single test case The preliminary results demonstrate the usefulness of our approach, which often exhaustively explores all paths and verifies two procedures as equivalent up to a given input size We are currently building an improved version of uc-klee that is capable of cross checking individual code patches rather than complete routines, thereby reducing the problems of path explosion Further, by jumping to the start of a patch, it will more robustly support code not easily checked by dynamic tools (such as device driver code) We plan to use this ability to check that kernel patches only remove errors or refactor code (for simplicity or performance) but not otherwise change existing functionality Acknowledgements The authors would like to thank Philip Guo, Diego Ongaro, and Amanda Ramos for their valuable feedback This work is supported by the United States Air Force Research Laboratory (AFRL) through Contract FA8650-10-C-7024 and by a National Science Foundation Graduate Research Fellowship under Grant No DGE-0645962 The paper’s words only represent the views of the authors References Brat, G., Havelund, K., Park, S., Visser, W.: Model checking programs In: IEEE International Conference on Automated Software Engineering, ASE 2000 (2000) Cadar, C., Dunbar, D., Engler, D.: KLEE: Unassisted and automatic generation of high-coverage tests for complex systems programs In: Proc of the Eighth Symposium on Operating Systems Design and Implementation (OSDI 2008), pp 209–224 (December 2008) 684 D.A Ramos and D.R Engler Cadar, C., Engler, D.: Execution generated test cases: How to make systems code crash itself In: Godefroid, P (ed.) SPIN 2005 LNCS, vol 3639, pp 2–23 Springer, Heidelberg (2005) Clarke, E., Kroening, D.: Hardware verification using ANSI-C programs as a reference In: Proc of the Asia and South Pacific Design Automation Conference, ASP-DAC 2003 (2003) Corbett, J.C., Dwyer, M.B., Hatcliff, J., Laubach, S., P˘ as˘ areanu, C.S.: Bandera: Extracting finite-state models from Java source code In: Proc of the 22nd International Conference on Software Engineering (ICSE 2000), pp 439–448 (June 2000) Deng, X., Lee, J.: Bogor/kiasan: A k-bounded symbolic execution for checking strong heap properties of open systems In: Proc of the 21st IEEE International Conference on Automated Software Engineering, pp 157–166 (2006) Elkarablieh, B., Marinov, D., Khurshid, S.: Efficient solving of structural constraints In: Proc of the International Symposium on Software Testing and Analysis, pp 39–50 (2008) Engler, D., Dunbar, D.: Under-constrained execution: making automatic code destruction easy and scalable In: Proc of the International Symposium on Software Testing and Analysis, ISSTA (July 2007) Engler, D., Yu Chen, D., Hallem, S., Chou, A., Chelf, B.: Bugs as deviant behavior: A general approach to inferring errors in systems code In: Proc of the 18th ACM Symposium on Operating Systems Principles, SOSP 2001 (2001) 10 Gligoric, M., Gvero, T., Jagannath, V., Khurshid, S., Kuncak, V., Marinov, D.: Test generation through programming in UDITA In: Proc of the 32nd International Conference on Software Engineering (ICSE 2010), pp 225–234 (2010) 11 Godefroid, P.: Model Checking for Programming Languages using VeriSoft In: Proc of the 24th Annual Symposium on Principles of Programming Languages (POPL 1997), pp 174–186 (January 1997) 12 Godefroid, P., Klarlund, N., Sen, K.: DART: Directed automated random testing In: Proc of the ACM SIGPLAN 2005 Conference on Programming Language Design and Implementation (PLDI 2005), pp 213–223 (June 2005) 13 Holzmann, G.J.: The model checker SPIN Software Engineering 23(5), 279–295 (1997) 14 Holzmann, G.J.: From code to models In: Proc of the Second International Conference on Applications of Concurrency to System Design, ACSD 2001 (June 2001) 15 Jones, R., Kelly, P.: Backwards-compatible bounds checking for arrays and pointers in C programs In: Proc of the International Workshop on Automatic Debugging (1997) 16 Khurshid, S., Pasareanu, C.S., Visser, W.: Generalized symbolic execution for model checking and testing In: Proc of the Ninth International Conference on Tools and Algorithms for the Construction and Analysis of Systems (2003) 17 Kuehlmann, A., Krohm, F.: Equivalence checking using cuts and heaps In: Proc of the 34th annual Design Automation Conference, DAC 1997, pp 263–268 (1997) 18 Marinov, D., Andoni, A., Daniliuc, D., Khurshid, S., and Rinard, M An evaluation of exhaustive testing for data structures Tech rep., MIT Computer Science and Artificial Intelligence Laboratory Report MIT-LCS-TR-921 (2003) 19 Mishchenko, A., Chatterjee, S., Brayton, R., Een, N.: Improvements to combinational equivalence checking In: Proc.of the 2006 IEEE/ACM International Conference on Computer-aided Design, ICCAD 2006, pp 836–843 (2006) Practical, Low-Effort Equivalence Verification of Real Code 685 20 Person, S., Dwyer, M.B., Elbaum, S., P˘ as˘ areanu, C.S.: Differential symbolic execution In: Proc of the 16th ACM SIGSOFT International Symposium on Foundations of Software Engineering (SIGSOFT ’08/FSE-16), pp 226–237 (2008) 21 Ruwase, O., Lam, M.S.: A practical dynamic buffer overflow detector In: Proc of the 11th Annual Network and Distributed System Security Symposium, pp 159–169 (2004) 22 Sen, K., Marinov, D., Agha, G.: CUTE: A concolic unit testing engine for C In: Proc of the 13th ACM SIGSOFT International Symposium on Foundations of Software Engineering (ESEC/FSE-13), pp 263–272 (September 2005) 23 Smith, E.W., Dill, D.L.: Automatic formal verification of block cipher implementations In: Proc of the 2008 International Conference on Formal Methods in Computer-Aided Design (FMCAD 2008), pp 1–7 (2008) Relational Abstractions for Continuous and Hybrid Systems Sriram Sankaranarayanan1 and Ashish Tiwari2 University of Colorado, Boulder, CO srirams@colorado.edu SRI International, Menlo Park, CA ashish.tiwari@sri.com Abstract In this paper, we define relational abstractions of hybrid systems A relational abstraction is obtained by replacing the continuous dynamics in each mode by a binary transition relation that relates a state of the system to any state that can potentially be reached at some future time instant using the continuous dynamics We construct relational abstractions by reusing template-based invariant generation techniques for continuous systems described by Ordinary Differential Equations (ODE) As a result, we abstract a given hybrid system as a purely discrete, infinite-state system We apply k-induction to this abstraction to prove safety properties, and use bounded model-checking to find potential falsifications We present the basic underpinnings of our approach and demonstrate its use on many benchmark systems to derive simple and usable abstractions Introduction In this paper, we present relational abstractions of hybrid systems A relational abstraction transforms a given hybrid system into a purely discrete transition system by summarizing the effect of the continuous evolution of states over time using relations The abstract discrete system is an infinite-state system that can be analyzed using standard techniques for verifying systems such as k-induction and bounded model checking Relational abstractions preserve the discrete behavior of the hybrid system and abstract only its continuous behavior They work by replacing the continuous dynamics in each mode by means of a relation R(x0 , x) The relation R relates a continuous state x0 with a state x that can be potentially reached at some future time instant, through some time trajectory of the system starting from x0 Such a relation R can be interpreted in two ways: (a) as a positive invariant set for an associated dynamical system over x0 , x, and (b) as a discrete transition relation that abstracts the evolution of the continuous states over time Sankaranarayanan’s work has been supported by NSF Career grant CNS-0953941 Tiwari’s work supported in part by DARPA under Contract No FA8650-10-C-7078, NSF grants CSR-0917398 and SHF:CSR-1017483 G Gopalakrishnan and S Qadeer (Eds.): CAV 2011, LNCS 6806, pp 686–702, 2011 c Springer-Verlag Berlin Heidelberg 2011 Relational Abstractions for Continuous and Hybrid Systems 687 The two views above provide two key advantages of the relational abstraction approach As a consequence of the first view, we can use techniques for generating invariants for continuous systems to generate a relational abstraction We propose simple extensions of template-based invariant generation techniques, which can abstract systems with linear as well as nonlinear dynamics, to construct relational abstractions Template-based techniques allow us to specify the form of the relational abstraction [9,19] Therefore, our technique can be used to obtain linear arithmetic relations for systems with nonlinear dynamics As a consequence of the second view, we obtain discrete infinite-state abstractions of hybrid systems This enables us to use techniques such as k-induction using decision procedures [37], abstract interpretation [11,21], or virtually any technique for discrete systems, to analyze hybrid systems It is well-known that the problem of verifying hybrid systems is quite hard, both in theory and in practice Recently, many advances have yielded remarkably efficient tools for integrating affine ODEs over sets and that work over large state spaces [24,5,39,16,35,17] However, we have observed that a significant gap in performance remains when these techniques are used to perform symbolic model checking, along the lines of tools such as HyTech and PHAVer [23,15] In our experience, this gap stems from the need to handle the dynamics repeatedly for the same mode, often with small variations between subproblems In this paper, we hypothesize that the situation with continuous dynamics is analogous to that of function calls encountered during program analysis During inter-procedural program analysis, it is often observed that the analysis of each function call, given the state at the entry to the call, is quite efficient However, the overall inter-procedural analysis is often not scalable due to repeated analysis of the same function with different actual parameters Therefore, as in the case of function calls in program analysis, we propose summarization techniques that abstract the effect of the dynamics in each mode by a discrete transition [27] As a result, our technique can efficiently handle continuous dynamics However, on the flip side, our approach may lose precision if the relational abstraction is too conservative Furthermore, the computation of relational invariants implicitly doubles the number of state variables Our approach is able to prove safety properties of hybrid systems using techniques such as k-induction, as well as to discover potential violations through bounded model checking To evaluate the idea of using relational abstractions of hybrid systems, we generate relational abstractions of some standard benchmarks and model check these abstractions We generate relational abstractions using a combination of quantifier elimination tools (REDLOG, QEPCAD) to search for templatized invariants [42,8,38], and polyhedral analysis of ODEs using fixed point iteration over cones [36] We analyze the resulting relational abstractions using the SAL framework from SRI [34,40] Our preliminary experiments are quite promising: our approach has the ability to prove properties of hybrid systems that are known to be complex, while at the same performing much more efficiently than symbolic model checkers The data from our exper- 688 S Sankaranarayanan and A Tiwari iments along with an extended version of this paper with proofs will be made available online1 We now discuss other related ideas in the literature Transition Invariants and Variance Analysis: The idea of defining “progress” invariant predicates over pairs of states, x, x, is well-known in the field of program analysis A lot of work has been done on verifying liveness properties using ranking functions, transition invariants, and progress invariants [4,30,10,18] However, there are some important distinctions between these various forms of relational invariants Transition invariants [30] capture the relationship between the current state and any previous state (at a particular program location) Transition invariants were used to prove termination Progress invariants capture the relationship between the current state and the immediately previous state (at a particular program location) [18] Progress invariants were used to compute complexity bounds of programs The relational abstractions presented here have a subtle difference: they capture the relationship between the current state and all previous states after the current mode was entered When combined with the entry and exit conditions of a mode, relational invariants are exactly summaries of that mode We use relational invariants to create abstractions of hybrid systems that can be used, for instance, to verify safety properties Podelski and Wagner provide a verification procedure for (region) stability properties of hybrid systems [31], where they derive binary reachability relations over trajectories of a hybrid system, similar to what is being proposed here However, there are two key differences in our methodology: (a) Our approach deals with the dynamics at each mode up front, deriving relational abstractions On the other hand, the technique of Podelski et al transforms the entire hybrid system, relying on safety verification built into a tool such as Phaver to derive the relations [15] Our goal in this paper is to make the process more efficient using constraint-based approaches and improve hybrid system safety verification in the first place (b) Second, our ultimate goal is to verify safety properties efficiently as opposed to verifying stability Abstractions of Hybrid Systems: Many different types of discrete abstractions have been studied for hybrid systems including predicate abstraction [2,41] and abstractions based on invariants [28] The use of counterexample-guided abstraction refinement for iterative refinement has also been investigated in the past (Cf Alur et al [2] and Clarke et al [7], for example) In this paper, the proposed abstraction yields a discrete but infinite state system Hybridization is a technique for converting nonlinear systems into affine systems by subdividing the invariant region into numerous subregions and approximating the dynamics as a hybrid system by means of a linear differential inclusion in each region [23,3,12] However, such a subdivision is expensive as the number of dimensions increases and often infeasible if the invariant region is unbounded Reachability Analysis: Reasoning about the reachable set of states for flows of nonlinear systems is an important primitive that is used repeatedly in the Cf http://www.csl.sri.com/~ tiwari/relational-abstraction/ Relational Abstractions for Continuous and Hybrid Systems 689 analysis of nonlinear hybrid systems This has been addressed using a wide variety of techniques in the past, including algebraic techniques, interval analysis, constraint propagation, and Bernstein polynomials [32,26,29,33,13] Preliminaries We present the basic definitions and properties of continuous systems defined by Ordinary Differential Equations (ODE) Let R denote the set of real numbers We use a, , z with subscripts to denote (column) vectors and A, , Z to denote matrices For an m × n matrix A, the row vector Ai , for ≤ i ≤ m, denotes the ith row We define continuous systems using vector fields Definition (Vector Field) A vector field F over a set X ⊆ Rn is a function F : X → Rn mapping each x ∈ X with a field direction F(x) Vector fields commonly arise from the definition of time-invariant systems A dxn time-invariant system defined by the ODE dx dt = f1 (x), , dt = fn (x) can be identified with the vector field F(x) = (f1 (x), , fn (x)) Therefore, a continuous system S : F, X is defined by a tuple consisting of the vector field F and a domain (also referred to as a mode invariant) X ⊆ Rn We now define the time trajectories of a continuous system: Definition (Time Trajectories) A time trajectory of a continuous system S : F, X is a function τ : [0, T ) → Rn for some T > 0, such that: τ (t) ∈ X, for all t ∈ [0, T ) and dτ dt = F(τ (t)), ∀ t ∈ [0, T ) Note To facilitate presentation, we have (deliberately) restricted our attention to time-invariant and autonomous systems The full generalization to time variant, non-autonomous systems will be presented in an extended version If the continuous system S is defined by a Lipschitz continuous vector field F, then for any x0 ∈ X, we can guarantee the existence of a unique time trajectory τ such that τ (0) = x0 [25] Henceforth, we will assume that the systems considered are defined by Lipschitz continuous vector fields An affine system S is a continuous system whose dynamics are defined by an affine vector field dx dt = Ax + b If f (x) is continuous and differentiable over x then we write ∂x f to denote the vector of its partial derivatives w.r.t each xi The Lie derivative of a function g with respect to a field F is given by LF (g) := (∂x g) · F(x), where ‘·’ computes the dot product of two vectors Positive Invariant Set: A set M ⊆ X is an invariant set for the system S iff for any x ∈ M , every time trajectory τ : [0, T ) → X such that τ (0) = x is entirely contained in M ; that is, (∀ t ∈ [0, T )) τ (t) ∈ M m Let M be a closed set defined by the assertion j=1 gj (x) ≤ for some finite m For technical reasons, we assume that each gj (x) is continuous and differentiable, and M is a “practical set” satisfying the constraint qualification (Cf Blanchini & Miani [6], page 104): (∀ x ∈ X), (∃z) gj (x) + ∂x gj · z < (1) 690 S Sankaranarayanan and A Tiwari R1 = 1KOhm VL L = 2mH S 5V VC 1mF R2 = 0.5KOhm Fig Circuit diagram for an LCR circuit with a voltage-controlled switch S Informally, the constraint qualifications ensure that j gj (x) < represents the (relative) interior of the set M and j gj (x) = represents the boundary It can be shown that all affine functions gj and positive-semidefinite quadratic forms (defining n-dimensional ellipsoids) satisfy these conditions Theorem The set M : m j=1 gj (x) ≤ is a positive invariant for the vector field F if for each j ∈ [1, m] the following assertion holds true: ∀ x ∈ X : gj (x) = ∧ i=j gi (x) ≤ ⇒ LF (gj ) < The theorem states that under appropriate conditions, a closed set M is a positive invariant set if the vector field F lies in the tangent cone at each point on the boundary of the set It is a direct consequence of Nagumo’s theorem, a more general result that holds for non-Lipschitz continuous dynamics and non-“practical” sets as well The theorem above provides a basis for various techniques for generating invariants for continuous systems using quantifier elimination and constraint solving [32,36,19,29] Hybrid Systems: Hybrid systems combine the continuous evolution of state with discrete, instantaneous jumps that can alter the state as well as the dynamics of a system [22] Definition (Hybrid System) A hybrid system H is defined by a set of discrete modes m1 , , mk , wherein, each mode mi is defined by a continuous system Si : Fi , Xi The system can change modes through a set of discrete transitions τ1 , , τm Each transition is defined by a prior mode m0 , a postmode m1 and a transition relation ρ[x, x ] ⊆ Xm0 × Xm1 , that relates the state x ∈ Xm0 before the transition to the state x ∈ Xm1 obtained as a result of taking the transition The initial conditions are given by the initial mode minit with the initial state set Θ ⊆ Xinit A hybrid system is a switched system if each discrete transition of the system does not modify the continuous state variables In other words, each discrete transition relation ρ[x, x ] can be written as ρ : γ(x) ∧ x = x, for guard γ(x) Relational Abstractions for Continuous and Hybrid Systems 691 Example (Switched system) Figure shows the circuit diagram for a voltagecontrolled switch that closes whenever the voltage across the capacitor (VC ) exceeds 4V , and opens whenever VC goes below 1V With the switch S open, the dynamics of the voltage across capacitor VC and dVL C the voltage across the inductor VL are given by dV dt = − VC − VL , dt = −5 + VC − VL Likewise, with the switch S closed, the dynamics of the voltage dVL C across the inductor are given by dV dt = − 3VC − VL , dt = −5 + 3VC − VL In each mode, we assume the mode invariant (VC , VL ) ∈ [−10, 10] × [−10, 10] Relational Abstractions We define relational abstractions for continuous systems, and present proof rules for checking that a given relation is an abstraction of the time trajectories of a continuous system defined by ODEs Let S : F, X be a continuous system defined by the vector field F, and domain (invariant) X It is assumed that S arises from a mode of a larger hybrid system Let R(x, y) be a relation over X × X Definition (Relational Abstraction Without Time) The relation R ⊆ R2n is a (timeless) relational abstraction of a continuous system S if for all time trajectories τ : [0, T ) → X of the system S, it is the case that (∀ t ∈ [0, T )) (τ (0), τ (t)) ∈ R Thus, for a time invariant system, a relational abstraction R captures all pairs of states (x, y) such that it is possible to reach y from x in a finite amount of time by evolving according to the dynamics of the system A relational abstraction R ⊆ X × X is said to be complete for a system S if whenever R(x, y) holds, there exists a time trajectory τ : [0, T ) → X such that τ (0) = x and τ (t) = y, for some time ≤ t < T Likewise, a relational abstraction R is linear if it can be expressed as an assertion in the theory of linear arithmetic over reals Note A continuous system whose dynamics are defined by constants (such as a mode of a multirate hybrid automaton) has a complete, linear relational dy abstraction For instance, the evolution of the ODE dx dt = 2, dt = −3 can be abstracted by the relation R(x, y, x , y ) := x − x ≥ ∧ 12 (x − x) = −1 (y − y) In fact, we can show that hybrid systems with constant dynamics in each mode are bisimilar to a purely discrete transition system through relationalization On the other hand, linear vector fields can fail to have complete abstractions We now define an “extended system” S from a given system S such that invariants of S will yield relational abstractions for S Definition (Extended System) Let S be a continuous system over x ∈ Rn defined by vector field F and invariant region X The extended system S has state variables (x, y) ∈ R2n with the dynamics dy dx = F(y), = 0, dt dt (2) 692 S Sankaranarayanan and A Tiwari invariant region given by X ×X and with the initial conditions x(0) = y(0) ∈ X We now refine the notion of positive invariants from Section to account for the presence of initial conditions in the system Definition (Initialized Positive Invariant) A set M is an initialized positive invariant for the system S with initial conditions X0 ⊆ M iff for all time trajectories τ : [0, T ) → Rn of S starting from τ (0) ∈ X0 we have τ (t) ∈ M for all t ∈ [0, T ) An initialized positive invariant is an over-approximation of all states reachable through a time trajectory starting from some pre-specified set of initial states This is, in fact, the true analog of an invariant for a program Note that every positive invariant set M (following the definition in Section 2) that contains the initial set X0 is an initialized positive invariant On the other hand, an initialized positive invariant may not be a general positive invariant This is because, it may be possible for trajectories that start from some state in the set M − X0 to exit the invariant set M Lemma A relation R is a relational abstraction of S if and only if R is an initialized positive invariant for S Proofs are provided in an extended version of the paper Therefore, if we can compute initialized positive invariants of the extended system S with initial states x(0) = y(0), we may use them to obtain relational abstractions In this work, we use various techniques that can compute positive invariants M (using the definition in Section 2) of systems S that contain some initial set of states X0 Theorem Let M be a positive invariant of the extended system S containing the initial states X0 = {(x, x) | x ∈ X} Then M is a relational abstraction of the system S Proof We note that a positive invariant M containing the initial states X0 is also an initialized positive invariant I.e, for any trajectory σ starting from X0 , we know that σ(t) ∈ M since σ(0) ∈ M The rest follows from Lemma The converse of the theorem above does not hold, in general As discussed above, a positive invariant M containing the initial set of states X0 is not necessarily an initialized positive invariant Note The extended system can be expressed, equivalently, using the (time reversed) system instead of the system (2), dx dy = 0, = −F(x) dt dt (3) with the initial conditions x(0) = y(0) In other words, a relational abstraction R(x, y) is a positive invariant of one of two dynamical systems: System where x is frozen in time and y evolves Relational Abstractions for Continuous and Hybrid Systems 693 according to the vector field F, and System where y is frozen in time and x evolves according to the time reversed field −F Proof Rule for Relational Abstractions: The proof rule for relational abstractions can be derived from the proof rule for invariant sets Furthermore, techniques for synthesizing invariants can be directly used to synthesize relational abstractions We now present a proof rule for checking if a relation R is a sound abstraction We assume that the relation R is specified as an assertion of the form R(x, y) : g1 (x, y) ≤ ∧ ∧ gm (x, y) ≤ , wherein g1 , , gm are continuous and differentiable functions over R2n Furthermore, for technical reasons, we assume that the set R ∩ (X × X) in R2n defined by the relation R restricted to X is a closed set and gj satisfy the constraint qualifications in (1) Definition The following rules allow us to conclude that the relation R, as specified above, is a relational abstraction of a continuous system S: Initialization: ∀ x ∈ X, R(x, x) , and Flow Preservation: We may use the rule for forward time: ∀j ∈ [1, m], ∀ x, y ∈ X, gi (x, y) ≤ ∧ gj (x, y) = ⇒ (∂y gj )·F(y) < , i=j or the rule for time reversed dynamics: ∀j ∈ [1, m], ∀x, y ∈ X, gi (x, y) ≤ ∧ gj (x, y) = ⇒ (∂x gj )·(−F(x)) < i=j Example We now consider relationalizations for the inductor-capacitorresistor (LCR) circuit in Example Consider the mode when the switch is dVL C open with dynamics given by dV dt = − VC − VL , dt = −5 + VC − VL We wish to show that the relation R(VC0 , VL0 , VC , VL ), represented by the assertion below, is a relational abstraction: (VC0 , VC , VL0 , VL ) ∈ [−10, 10]4 ∧ VC + 5VL ≤ VC0 + 50 ∧ 4VL ≤ VL0 + 30 ∧ 2VL − 3VC ≤ 2VL0 + 30 Let us consider the inequality VC + 5VL − VC0 − 50 ≤ For the initial condition, we set VC = VC0 and VL = VL0 and verify that 5VL0 ≤ 50 holds over the invariant region (VC0 , VL0 ) ∈ [−10, 10]2 Likewise, the Lie derivative of the left-hand side expression is given by 4VC − 6VL − 20 We verify the following entailment using an SMT solver R(VC0 , VL0 , VC , VL ) ∧ VC + 5VL − VC0 − 50 = |= 4VC − 6VL − 20 < The remaining constraints are similarly verified Disjunctive Relational Abstraction: Often, the relational abstraction can m be represented as the disjunction R(x, y) : j=1 Rj (x, y) of finitely many relations R1 , , Rm , such that (a) each relation Rj is represented by an assertion over x, y satisfying the flow preservation proof rule in Definition 7, and (b) the disjunctive relation R(x, y) satisfies the initialization rule 694 S Sankaranarayanan and A Tiwari Example Consider, once again, the LCR circuit in Example The relation below is a disjunctive relational abstraction for the switch open mode: |VL | ≤ max (|VL0 |, |VC0 − 5|) ∧ |VC − 5| ≤ max (|VL0 |, |VC0 − 5|) Verifying this fact can be performed by expanding the definitions of max and | · | The resulting assertion is cast in the disjunctive normal form, and the flow preservation proof rule in Definition can be checked for each disjunct The initialization rule can be checked for the whole disjunction 3.1 Relational Abstractions of Hybrid Systems A relational abstraction of a hybrid system is constructed by replacing each constituent continuous system by its relational abstraction and keeping the discrete transitions unchanged Specifically, if H is a hybrid system (Definition 3) with k modes and n real-valued variables, then the relational abstraction of H is a state transition system over the state space {1, , k} × Rn whose transition relation is the union of the discrete transitions of H and the relational abstractions of the k modes of H Several classes of hybrid automata, such as timed automata and linear hybrid automata, have complete relational abstractions Since the discrete transitions are not abstracted, we only need to ensure that the relational abstraction of the continuous dynamics are complete Timed Automata: The continuous dynamics of a timed automata with n clocks, x1 , , xn , can be abstracted by the relation ∧ni=2 (x1 − x10 = xi − xi0 ) ∧ x1 ≥ x10 It is easy to check that this is a complete abstraction Multirate Automata: The continuous dynamics defined by ODEs dx dt = dxn c1 , , dt = cn , where c1 , , cn are nonzero constants, can be abstracted by 10 i0 10 the relation ∧ni=2 ( x1 −x = xi −x ) ∧ x1 −x ≥ Again, it is easy to check c1 ci c1 that this is a complete abstraction Note that the result for timed automata is obtained as a special case where all ci are Rectangular Automata: In rectangular automata, the dynamics in each dxn mode are specified as a1 ≤ dx dt ≤ b1 , , an ≤ dt ≤ bn Assuming < ≤ bi for all i, these dynamics can be abstracted by the relation ≤ max x1 − x10 xn − xn0 , , b1 bn ≤ x1 − x10 xn − xn0 , , a1 an Again, it is easy to check that this is a complete abstraction Linear Hybrid Automata: In linear hybrid automata, the dynamics in ˙ over the dotted variables x ˙ each mode are specified as a linear constraint φ(x) Without loss of generality, we can restrict φ to be of the form A1 x˙ ≤ b1 ∧ A2 x˙ ≥ b2 , where A1 , A2 are n×n rational matrices and b1 , b2 are n×1 vectors consisting of positive rationals These dynamics can be abstracted by the relation ≤ max(A1 (x − x0 )./b1 ) ≤ min(A2 (x − x0 )./b2 ) Relational Abstractions for Continuous and Hybrid Systems Hybrid System Invariant Generator Discrete System 695 Counterexample k-induction or Proof BMC (SAL) Fig Framework for implementing a safety verification engine using relationalization where / is componentwise division This is again a complete abstraction Note that the result for rectangular automata is obtained as a special case where A1 , A2 are identity matrices Linear Systems with Rational Eigenvalues: First consider the linear system dx dt = Dx, where D is a diagonal matrix with rational entries λ1 , , λn For simplicity assume λi = for all i Since they are rational, the λi ’s can be written as integer multiples of some base rational λ, that is, λ1 = c1 λ, , λn = cn λ for some rational λ and integers c1 , , cn A complete relational abstraction of the linear system is given by n [xi = rci xi0 ] (∃r > 0) i=1 If A is not diagonal, but diagonalizable with all rational eigenvalues, then a relational abstraction can be obtained in the same way after doing a change of variables transformation If A is nilpotent, then again the linear system can be shown to have a complete relational abstraction Implementation Figure shows the overall verification framework It consists of two parts: (a) an invariant generator for generating the relational abstraction of the input hybrid system, and (b) a verifier for analyzing the relational abstraction using techniques such as k-induction and bounded model checking (BMC) Note that other verification techniques/tools are equally applicable here Our framework abstracts each mode up front It is possible, in practice, to implement the abstraction on-the-fly, whenever a previously unseen mode is entered We now discuss the implementation of relational abstraction, restricting our attention here to techniques that have been employed in our experiments We primarily apply template-based methods for generating relational abstractions [9,19] Template-based techniques formulate an unknown parameterized form for the required invariant and cast the problem of generating the invariant as an ∃∀ formula These ∃∀ formulas can be solved directly using quantifier elimination techniques over the theory of reals [42,8], or they can be first converted into ∃ formulas through dualization The ∃ formulas, which contain nonlinear constraints over the unknown parameters, can be solved using either fixed point iteration over cones [36], or using bit-vector solvers [19], or by simulating the system numerically [20] In our experiments, we use a specialized quantifier elimination technique [38] and the tool TimePass, which implements a fixed point ... automated input generation, dynamic tainting, and generation and evaluation of candidate attack strings One component of Ardilla, the attack generator, creates candidate attack strings from a. .. Organization Additional Reviewers A Abraham, Erika Ait Mohamed, Otmane Alglave, Jade Andres, Miguel E Asarin, Eugene Atig, Faouzi B Baier, Christel Balakrishnan, Gogul Barakat, Kamal Batty, Mark Bauer, Andreas... Mador-Haim, Sela Maeda, Naoto Majumdar, Rupak Maler, Oded Malkis, Alexander Maoz, Shahar Mardare, Radu Mateescu, Maria Mayr, Richard Mereacre, Alexandru Merschen, Daniel Might, Matthew Miner, Paul

Ngày đăng: 12/12/2017, 08:23

Từ khóa liên quan

Mục lục

  • Cover

  • Front matter

  • 1. HAMPI: A String Solver for Testing, Analysis and Vulnerability Detection

    • HAMPI: A String Solver for Testing, Analysis and Vulnerability Detection

      • Introduction

        • Paper Organization

        • Example: SQL Injection

        • The Hampi String Constraint Solver

          • Hampi Input Language for String Constraints

          • Core Form of String Constraints

          • Bit-Vector Encoding and Solving

          • Example of Hampi Constraint Solving

          • Evaluation

            • Identifying SQL Injection Vulnerabilities Using Static Analysis

            • Creating SQL Injection Attacks Using Dynamic Analysis

            • Systematic Testing of C Programs

            • Related Work

            • References

            • 2. Using Types for Software Verification

              • Using Types for Software Verification

              • 3. SMT-Based Modular Analysis of Sequential Systems Code

                • SMT-Based Modular Analysis of Sequential Systems Code

                  • Introduction

                  • Basic Memory Model

                  • Types

                    • Formalizing Types

                    • SMT Theory for Types

                    • Low-Level Data Structures

                      • Reachability Predicate

                      • Modeling Low-Level Lists

Tài liệu cùng người dùng

  • Đang cập nhật ...

Tài liệu liên quan