David Evans. LCLint User's Guide, February 1996. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Automatic Generation and Checking of Program Specifications - Nimmer, Ernst (2001) (2 citations) (Correct)
....5. Another obvious way to extend this work is to use different invariant detectors than Daikon or different verifiers than ESC Java. Section 6 lists some other invariant detectors. Examples of static verifiers that are connected with real programming languages include LCLint [EGHT94, Eva96, Eva00] ACL2 [KM97] LOOP [JvH 98] Java PathFinder [HP00] and Bandera [CDH 00] We are currently integrating Daikon with IOA [GLV97, GL00] a formal language for describing computational processes that are modeled using I O automata [Lyn96, LT87, LT89] The IOA toolset ....
David Evans. LCLint User's Guide, Version 2.5, May 2000. http://lclint.cs.virginia.edu/guide/. 11
Compile-Time Debugging of C Programs Working on Trees - Elgaard, Møller.. (2000) (13 citations) (Correct)
....Second, traditional compiler technologies such as program slicing [21] pointer analysis [7] and shape analysis [19] are used in tools like CodeSurfer [8] and Aspect [10] that conservatively detect known causes of errors. Third, full scale program verification is attempted by tools like LCLint [6] and ESC [5] which capture runtime behavior as formulas and then appeal to general theorem provers. All three approaches lead to tools that are either incomplete or unsound (or both) even for straight line code. In practice, this may be perfectly acceptable if a significant number of real ....
David Evans. LCLint user's guide. URL: http://www.sds.lcs.mit.edu/ lclint/guide/.
Compile-Time Debugging of C Programs Working on Trees - Elgaard, Møller, Schwartzbach (2000) (13 citations) (Correct)
....their sources. Second, traditional compiler technologies such as program slicing, pointer analysis, and shape analysis are used in tools like CodeSurfer [7] and Aspect [9] that conservatively detect known causes of errors. Third, full scale program verification is attempted by tools like LCLint [6] and ESC [5] which capture runtime behavior as formulas and then appeal to general theorem provers. All three approaches lead to tools that are either incomplete or unsound (or both) even for straight line code. In practice, this may be perfectly acceptable if a significant number of real ....
David Evans. LCLint user's guide. URL: http://www.sds.lcs.mit.edu/ lclint/guide/.
An Empirical Analysis of C Preprocessor Use - Ernst, Badros, Notkin (2000) (4 citations) (Correct)
.... rather than in their own right. A survey of nine C static checkers [MK97] mentions the macro preprocessor only in terms of whether such warnings can be turned o# in the tools; however, that paper focuses on coding style likely to lead to errors rather than on lexical issues. LCLint [EGHT94, Eva96] allows the programmer to add annotations that enable more sophisticated checks than many other lint programs. LCLint optionally checks function like macros that is, those that take arguments for macro arguments on the left hand side of assignments, for statements playing the role of ....
David Evans. LCLint User's Guide, August 1996. http://www.sds.lcs.mit.edu/lclint/guide/.
An Empirical Analysis of C Preprocessor Use - Ernst, Badros, Notkin (1999) (4 citations) (Correct)
.... rather than in their own right. A survey of nine C static checkers [MK97] mentions the macro preprocessor only in terms of whether such warnings can be turned off in the tools; however, that paper focuses on coding style likely to lead to errors rather than on lexical issues. LCLint [EGHT94, Eva96] allows the programmer to add annotations that enable more sophisticated checks than many other lint programs. LCLint optionally checks function like macros that is, those that take arguments for macro arguments on the left hand side of assignments, for statements playing the role of ....
David Evans. LCLint User's Guide, August 1996. Version 2.2. http://larch-www.lcs.mit.edu:8001/larch/ lclint/guide/guide.html.
An Empirical Analysis of C Preprocessor Use - Ernst, Badros, Notkin (1997) (4 citations) (Correct)
....or braces. The latter are often used to create a block and perform actions that must occur at its beginning and end, as for BEGINGCPROTECT and ENDGCPROTECT. 2 By contrast, LCLint considers assignment to a macro argument dangerous but does not appear to check for assignments to local variables. [Eva96a] 3 Since the body is already a complete statement, the extra semicolon can cause problems such as mis parsing of nested if statements. Such macros can be confusing to use, because programmers are inclined to add a semicolon after invocations that look like functions; wrapping the body in do ....
David Evans. LCLint User's Guide, version 2.2 edition, August 1996. http://larchwww. lcs.mit.edu:8001/larch/lclint/guide/guide.html.
Teaching Software Engineering Using Lightweight Analysis - Evans (2001) Self-citation (Evans) (Correct)
....tools that provide substantial and immediate benefits relative to the effort required to use them. The range of tools we select provides a sampling of the design space of analysis tools where efficiency, effort required, soundness and completeness are often conflicting goals. LCLint LCLint [EGHT94, Evans96, Evans00] is an annotation assisted lightweight static checking tool for C developed through a joint research project by the University of Virginia, MIT and Compaq SRC. LCLint is designed to be as efficient and easy to use as a compiler. If minimal effort is invested adding annotations to programs, LCLint ....
David Evans. LCLint User's Guide. Version 2.5. May 2000. http://lclint.cs.virginia.edu/.
LCLint: A Tool for Using Specifications to Check Code - Evans (1994) (61 citations) Self-citation (Evans) (Correct)
No context found.
David Evans. LCLint User's Guide, Version 1.4. September 1994. Available in: ftp://larch.lcs.mit.edu/pub/Larch/ lclint/lclint1.4.userguide.ps.Z
Finding User/Kernel Pointer Bugs With Type Inference - Rob Johnson David (2004) (2 citations) (Correct)
No context found.
David Evans. LCLint User's Guide, February 1996.
Rob Johnson David Wagner - Report No Ucb (Correct)
No context found.
David Evans. LCLint User's Guide, February 1996.
An Empirical Analysis of C Preprocessor Use - Ernst, Badros, Notkin (2002) (4 citations) (Correct)
No context found.
D. Evans, LCLint User's Guide, Aug. 1996, http://lclint.cs.virginia. edu/guide/.
Static verification of dynamically detected program.. - Nimmer, Ernst (2001) (11 citations) (Correct)
No context found.
David Evans. LCLint User's Guide, Version 2.5, May 2000. http://lclint. cs.virginia.edu/guide/.
Finding User/Kernel Pointer Bugs With Type Inference - Rob Johnson David (2004) (2 citations) (Correct)
No context found.
David Evans. LCLint User's Guide, February 1996.
Finding User/Kernel Pointer Bugs With Type Inference - Rob Johnson David (2004) (2 citations) (Correct)
No context found.
David Evans. LCLint User's Guide, February 1996.
An Empirical Analysis of C Preprocessor Use - Ernst, Badros, Notkin (2002) (4 citations) (Correct)
No context found.
D. Evans, LCLint User's Guide, Aug. 1996, http://lclint.cs.virginia. edu/guide/.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC