-
Notifications
You must be signed in to change notification settings - Fork 1
/
INSTALL.txt
executable file
·133 lines (91 loc) · 4.3 KB
/
INSTALL.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
Copyright (c) 2010, Cormac Flanagan (University of California, Santa Cruz)
and Stephen Freund (Williams College)
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided
with the distribution.
* Neither the names of the University of California, Santa Cruz
and Williams College nor the names of its contributors may be
used to endorse or promote products derived from this software
without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
To Install:
-----------
1. You will need Ant, Java 1.7, and cpp to build RoadRunner.
The $JAVA_HOME environment variable must point to the proper
Java distribution. (Depending on the Java version, you may need
to add tools.jar from the JDK to your classpath in build.xml or
in Eclipse.)
2. Unzip the dist file, and cd into the top-level directory.
3. Build the source:
> cd RoadRunner; ant
To Run:
-------
1. cd RoadRunner
2. source msetup
Note: this sets up environment variables and configures
everything for Java 1.7.
3. Test it:
> javac test/Test.java
> rrrun test.Test
You should get no errors.
> rrrun -tool=TL:RS:LS test.Test
You should get many race errors on field Test.y.
4. Look at options:
> rrrun -help
You will at least want to look at the following:
-quiet
-help
-classpath={String}
-toolpath={String}
-tool={String}
-classes={StringMatcher}
-fields={StringMatcher}
-methods={StringMatcher}
-array={ArrayMode}
-field={FieldMode}
-nobarrier
5. Look at sample tools:
> rrrun -tools
Look at rr.tool.Tool abstract class and sample tools for
implementation info.
6. Running on benchmarks:
When performing comparisions to other analysis platforms, you will
need to pay particular attention to several options, including
-array and -field to ensure memory is instrumented as you intend.
In addition, RoadRunner includes specialized handling of various
barrier implementations to facilitate writing analyses that must
treat barriers specially. However, it assumes those barriers are
correct, which is not the case for some benchmarks, including
the barriers in JavaGrande. Thus, you will miss errors unless
you specify the "-nobarrier" flag to not treat barrier code
specially.
ECLIPSE SUPPORT:
-----------
After building as described above, you can import the RoadRunner directory
as an existing project.
Refresh, Clean, etc. should rebuild everything as
necessary. The "rrrun script" will pick up any modifications you made.
If adding new Tools, changing abbreviations, tools paths, changing the ClassLoader,
changing the agent, or doing anything else unusual, you should rebuilt
RoadRunner with the build.xml ant script to ensure all the auto-generated
files are in sync.
There is a sample launch script "scripts/RRMain-tools.launch" to print out all
the supported tools from inside Eclipse if you wish to work exclusively
in the Eclipse environment.