You can reproduce the experiments under the provided VM. The experiments were re-run
and the results are stored under theVM.

Caveat: Unfortunately, since a real mailbox file was used for the original
experiments with Pine, we cannot make it available. As a replacement, we provide a “dummy”
mailboxes containing the same number of e-mails as the ones used in the originalexperiments.

If you have any further questions about the VM or you spot an issue, please contact
TomaszKuchta.

Directory structure

/home/docovery : the home directory for the “docovery”user

/home/docovery/docovery : the main directory ofinterest

/home/docovery/docovery/benchmarks : this is where the files and the
associated applications arestored

./FILES : files (for libdwarf and
binutils also the original filesprovided)

./benchmarks : directory, where all the applications used for experiments werebuilt

The structure of the results directory at the example ofprConcolicNativeCyclicConstrOptCexCache.xml:

a list of directories, named after the files under test; for out example these
are 1p-end, 2p-end, 4p-end, 8p-end, 16p-end, 32p-end,
64p-end, 128p-end, 256p-end

inside each of these directories you will find klee-last directory containing the Docovery execution-related
files and the recovery results

klee-last/doc-recov-data/recovery subdir contains all the recovery candidates in directories named
ConstraintSet_NUMBER; each such directory corresponds to one execution
path; ConstraintSet_00001_fail always corresponds to the original execution path
taken by the application when processing the brokenfile

native directory storing native executable of the application and used to
verifycandidates

doc-recov directory containing a symbolic link to Docoveryexecutable

log files for test, status, stdout andstderr

the xml test fileitself

a *.bc file : an LLVM bit code for the tested application; in our example that
is pr.bc

a bunch of helper informationfiles

Tip: If you have an access to an SMTP server, you may find smtp-server
and email options of the au-tom-ator infrastructure useful
(see au-tom-ator help fordetails)