The Daikon Invariant Detector User Manual_ 4. Running Daikon

The Daikon Invariant Detector User Manual_ 4. Running...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
[ < ] [ > ] [ << ] [ Up ] [ >> ] [ Top ] [ Contents ] [ Index ] [ ? ] 4. Running Daikon This section describes how to run Daikon on a data trace (‘ .dtrace ’) file, and describes Daikon's command-line options. This section assumes you have already run a front end (e.g., an instrumenter) to produce a ‘ .dtrace ’ file (and optionally ‘ .decl ’ and ‘ .spinfo ’ files); to learn more about that process, see section Example usage for Java, C/C++, Perl, and Eiffel , and see section Front ends (instrumentation) . Run the Daikon invariant detector via the command java daikon.Daikon [flags] dtrace-files. .. [decl-files. ..] [spinfo-files. ..] The dtrace-files are data trace (‘ .dtrace ’) files containing variable values from an execution of the target program. The decl-files are declaration (‘ .decl ’) files containing program point declarations. Be sure to include all declaration files that are needed for the particular data trace file; the simplest way is to include every declaration file created when instrumenting the program. Not all Daikon front ends produce ‘ .decl ’ files, since program point declarations may also appear in .dtrace ’ files. For instance, the Chicory front end for Java (see section Java front end Chicory ) produces only ‘ .dtrace ’ files. If there are no ‘ .decl ’ files, then it is not necessary to include them on the command line to Daikon. The spinfo-files are splitter info (‘ .spinfo ’) files that enable detection of conditional invariants (see section Conditional invariants and implications ); these are optional and may be created automatically or by hand. The files may appear in any order; the file type is determined by whether the file name contains ‘ .decls ’, .dtrace ’, or ‘ .spinfo ’. As a special case, a file name of ‘ - ’ means to read data trace information from standard input. The optional flags are described in the sections that follow. For further ways to control Daikon's behavior via configuration options, see Configuration options , and see the list of options to the front end such as Chicory (see section Chicory options ) or Kvasir (see section Kvasir options ). 4.1 Options to control Daikon output 4.2 Options to control invariant detection 4.3 Processing only part of the trace file 4.4 Daikon configuration options 4.5 Daikon debugging options [ < ] [ > << ] [ ] [ >> ] [ Contents ] [ Index ] [ ? ] 4.1 Options to control Daikon output --help The Daikon Invariant Detector User Manual: 4. Running Daikon file:///C:/Users/tyalanf/AppData/Local/Temp/ .. 2/24/2012 12:16 PM You created this PDF from an application that is not licensed to print to novaPDF printer ( )
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Print usage message. -o inv_file Output serialized invariants to the specified file; they can later be postprocessed, compared, etc. Default: ‘ basename .inv.gz ’ in the current directory, where the first data trace file's basename starts with ‘ basename .dtrace ’. Default is no serialized output, if no such data trace file was supplied. If a data trace file was supplied, there is currently no way to avoid creating a serialized invariant file.
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 02/24/2012 for the course CSE 503 taught by Professor Davidnotikin during the Spring '11 term at University of Washington.

Page1 / 6

The Daikon Invariant Detector User Manual_ 4. Running...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online