1 wsdiff(1) User Commands wsdiff(1)
2
3
4
5 wsdiff - report differences between proto area objects
6
7 SYNOPSIS
8 wsdiff [-dvVst] [-r results] [-i filelist] old new
9
10 DESCRIPTION
11 The wsdiff utility detects and reports on object differences found
12 between two proto areas constructed from the same workspace. This can
13 be useful when trying to understand which objects have changed as a
14 result of a particular source change.
15
16 old specifies the baseline proto area constructed without the source
17 change. new specifies the proto area constructed with the source
18 change. Both old and new should be constructed from the same workspace,
19 otherwise wsdiff will find object differences not associated with the
20 source change.
21
123 > lgrp_cpu_init+0x164: d8 76 a0 30 stx %o4, [%i2 + 0x30]
124 > lgrp_cpu_init+0x168: d6 04 e0 00 ld [%l3], %o3
125 > lgrp_cpu_init+0x16c: 80 a2 e0 00 cmp %o3, 0x0
126
127
128
129 Example 3: Using an input file list
130
131 The -i option tells wsdiff to compare a specific list of objects. This
132 can be useful in conjunction with other options that direct wsdiff to
133 log more verbosely, allowing one to "drill down" into a particular
134 object's differences:
135
136 user@example$ echo "usr/lib/mdb/kvm/sparcv9/genunix.so" > flist
137 user@example$ wsdiff -vV -r results -i flist proto.old proto
138 usr/lib/mdb/kvm/sparcv9/genunix.so
139
140 user@example$ cat results
141 <... verbose differences only for genunix.so ...>
142
143 Example 4: Invoking wsdiff through nightly(1)
144
145 By specifying -w in NIGHTLY_OPTIONS, nightly(1) will use wsdiff(1) to
146 determine which objects look different, compared to the previous build.
147 A pre-existing proto area must exist for wsdiff(1) to compare against.
148 nightly(1) will move aside the pre-existing proto area (renaming it to
149 $ROOT.prev under proto), and will invoke wsdiff at the end of the
150 build. The list of changed objects will be reported in the nightly mail
151 message, and a results file "wsdiff_results" will appear in the nightly
152 log area.
153
154 Example 5: Influencing the level of paralelism
155
156 wsdiff spawns a number of threads by default after it determines the
157 list of files for comparison. Default number of threads is based on the
158 number of on-line CPUs present in the system. To set the number of
159 threads for processing to some other value the DMAKE_MAX_JOBS
160 environment variable can be used:
161
162 $ DMAKE_MAX_JOBS=24 wsdiff proto_base proto_patch
163
164 Note that this variable is also used for nightly(1) so when run from
165 nightly(1), wsdiff will honor the setting.
166
167 SEE ALSO
168 lintdump(1), nightly(1), elfdump(1),
169
170
171
172 15 Jul 2010 wsdiff(1)
|
1 wsdiff(1ONBLD) illumos Build Tools wsdiff(1ONBLD)
2
3
4
5 wsdiff - report differences between proto area objects
6
7 SYNOPSIS
8 wsdiff [-dvVst] [-r results] [-i filelist] old new
9
10 DESCRIPTION
11 The wsdiff utility detects and reports on object differences found
12 between two proto areas constructed from the same workspace. This can
13 be useful when trying to understand which objects have changed as a
14 result of a particular source change.
15
16 old specifies the baseline proto area constructed without the source
17 change. new specifies the proto area constructed with the source
18 change. Both old and new should be constructed from the same workspace,
19 otherwise wsdiff will find object differences not associated with the
20 source change.
21
123 > lgrp_cpu_init+0x164: d8 76 a0 30 stx %o4, [%i2 + 0x30]
124 > lgrp_cpu_init+0x168: d6 04 e0 00 ld [%l3], %o3
125 > lgrp_cpu_init+0x16c: 80 a2 e0 00 cmp %o3, 0x0
126
127
128
129 Example 3: Using an input file list
130
131 The -i option tells wsdiff to compare a specific list of objects. This
132 can be useful in conjunction with other options that direct wsdiff to
133 log more verbosely, allowing one to "drill down" into a particular
134 object's differences:
135
136 user@example$ echo "usr/lib/mdb/kvm/sparcv9/genunix.so" > flist
137 user@example$ wsdiff -vV -r results -i flist proto.old proto
138 usr/lib/mdb/kvm/sparcv9/genunix.so
139
140 user@example$ cat results
141 <... verbose differences only for genunix.so ...>
142
143 Example 4: Invoking wsdiff through nightly(1ONBLD)
144
145 By specifying -w in NIGHTLY_OPTIONS, nightly(1ONBLD) will use
146 wsdiff(1ONBLD) to determine which objects look different, compared to
147 the previous build. A pre-existing proto area must exist for
148 wsdiff(1ONBLD) to compare against. nightly(1ONBLD) will move aside the
149 pre-existing proto area (renaming it to $ROOT.prev under proto), and
150 will invoke wsdiff at the end of the build. The list of changed objects
151 will be reported in the nightly mail message, and a results file
152 "wsdiff_results" will appear in the nightly log area.
153
154 Example 5: Influencing the level of paralelism
155
156 wsdiff spawns a number of threads by default after it determines the
157 list of files for comparison. Default number of threads is based on the
158 number of on-line CPUs present in the system. To set the number of
159 threads for processing to some other value the DMAKE_MAX_JOBS
160 environment variable can be used:
161
162 $ DMAKE_MAX_JOBS=24 wsdiff proto_base proto_patch
163
164 Note that this variable is also used for nightly(1ONBLD) so when run
165 from nightly(1ONBLD), wsdiff will honor the setting.
166
167 SEE ALSO
168 nightly(1ONBLD), elfdump(1),
169
170
171
172 15 Jul 2010 wsdiff(1ONBLD)
|