2724
by Nicolas Palix
Add coccicheck script |
1 |
Coccicheck version 0.2.4 |
2911
by Nicolas Palix
Upgrade version number of Coccicheck |
2 |
|
2724
by Nicolas Palix
Add coccicheck script |
3 |
-*- Usage -*-
|
4 |
||
5 |
1) ./configure mode <your project directory> |
|
2763
by Julia Lawall
fix readme |
6 |
This will setup some default directories. |
2724
by Nicolas Palix
Add coccicheck script |
7 |
Check in Makefile if they suit you! |
2821
by Nicolas Palix
Better coordination between coccinelle and coccicheck |
8 |
mode is either org or diff, depending on whether you want the |
2763
by Julia Lawall
fix readme |
9 |
output in Emacs org mode, or in diff format where - indicates not |
10 |
something to remove but an item of interest. |
|
11 |
||
2724
by Nicolas Palix
Add coccicheck script |
12 |
NB: The project directory must currently be an absolute path. |
2821
by Nicolas Palix
Better coordination between coccinelle and coccicheck |
13 |
|
14 |
On bash, you can overwrite the default flags on the command line: |
|
2891
by Nicolas Palix
Change information in README |
15 |
SPFLAGS="-I my_include -timeout 30" ./configure mode <project> |
2833
by Nicolas Palix
Add a note about overwriting the default flags |
16 |
|
17 |
2) make update |
|
2724
by Nicolas Palix
Add coccicheck script |
18 |
This will create the `results` directory. |
19 |
It will contain all the files needed |
|
20 |
to apply the SmPL files to your project. |
|
21 |
||
22 |
3) make [-jX] (where X is the number of cores to use) |
|
23 |
This will apply all the SmPL files found in |
|
24 |
the `cocci` directory to your project |
|
25 |
(as previously defined). |
|
26 |
||
27 |
When it's done, you will get some "out" and "log" files in the |
|
28 |
`results` directory. "out" files will contain the output generated by |
|
29 |
the SmPL files, and the "log" files will contain the execution trace |
|
30 |
of spatch. |
|
31 |
||
32 |
If you edit/add some SmPL files in `cocci` directory, you can use |
|
2763
by Julia Lawall
fix readme |
33 |
`make checkcocci` to parse them and see if there is any error. |
2724
by Nicolas Palix
Add coccicheck script |
34 |
|
35 |
Once the results are computed, you can either: |
|
2763
by Julia Lawall
fix readme |
36 |
- run `make viewres` to view all the bug reports |
2891
by Nicolas Palix
Change information in README |
37 |
- run `make viewlog` to view the complete execution trace |
38 |
- run `make viewfilteredlog` to only view unlikely errors of the trace |
|
4116.2.67
by Sébastien Hinderer
Remove a bunch of trailing whitespaces and blank lines at end of files. |
39 |
Note that this filter will remove some error messages about |
2891
by Nicolas Palix
Change information in README |
40 |
timeout, parsing ... Check Makefile to see the exact list. |
41 |