ECLAIR

ECLAIR is a commercial static code analysis tool developed by BUGSENG, LLC for automatic analysis, verification, testing and transformation of C and C++ programs.

This article is about the software. For other uses, see Éclair (disambiguation).
ECLAIR
Developer(s)BUGSENG, LLC
Stable release
1.2 / November 12, 2012 (2012-11-12)
Operating systemCross-platform
TypeStatic code analysis
LicenseProprietary
Websitebugseng.com/products/eclair

Capabilities

ECLAIR is a complete re-engineering of a series of prototypes[1] developed at the Applied Formal Methods Laboratory of the University of Parma. It uses formal methods-based static code analysis techniques such as abstract interpretation and model checking combined with constraint satisfaction techniques to detect or prove the absence of certain run time errors in source code, and provides support for program analysis and verification, program test generation and program transformation.

Concerning program analysis and verification, ECLAIR can statically detect or proof the absence of run-time anomalies as well as automatically check for conformance with respect to several coding standards, such as MISRA C, MISRA C++, CERT C Secure Coding Standard, CERT C++ Secure Coding Standard,[2] High-Integrity C++, NASA/JPL C, ESA/BSSC C/C++, JSF C++, EC--,[3] Netrino Embedded C,[4] The Power of Ten (C),[5] Industrial Strength C++.[6]

For program testing, ECLAIR can automatically synthesize sets of unit test inputs that reach a user-specified coverage criterion, warning the user when, due to infeasible conditions in the program, this coverage cannot be attained.

Regarding program transformation, ECLAIR can be used to perform complex program transformations: these are specified by syntactic and semantics-based criteria; the program regions in the source that match these criteria can be optionally replaced by a parametrized substitution.

gollark: This would be easier if I actually knew anything about which frequencies each index corresponds to, hmm.
gollark: Maybe I should take the logarithm of it instead.
gollark: I realized it might be easier to graph this, so... here you go?
gollark: Sure.
gollark: It says the biggest thing is at... index 0?

See also

References
  1. R. Bagnara; P. M. Hill; E. Zaffanella (2007). "A Prolog-based Environment for Reasoning about Programming Languages". arXiv:0711.0345 [cs.PL].
  2. Seacord, Robert C. (2013). Secure Coding in C and C++. SEI Series in Software Engineering (2nd ed.). Addison-Wesley Professional. ISBN 978-0-321-82213-0.
  3. Hatton, L. (2005). "EC—a measurement based safer subset of ISO C suitable for embedded system development". Information and Software Technology. 47 (3): 181–695. CiteSeerX 10.1.1.101.7828. doi:10.1016/j.infsof.2004.08.001.
  4. Barr, Michael (2008). Embedded C Coding Standard. Barr Group. ISBN 978-1442164826.
  5. Gerald, J. (2006). "The Power of 10: Rules for Developing Safety-Critical Code". Computer. 39 (6): 95–97. doi:10.1109/MC.2006.212.
  6. Henricson, Mats; Nyquist, Erik (1997). Industrial Strength C++. Prentice-Hall PTR. ISBN 978-0131209657.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.