On Tue, 3 Jan 2012, Artem Bityutskiy wrote:
On Tue, 2012-01-03 at 16:46 +0100, Robert Gomulka wrote:
Hi all,
a few days ago I started using Coccinelle as a tool for improving my
source code. The tool is pretty impressive, although I must admit
learning curve is quite steep for me.
Unfortunately I am unable to fully automate the checks (found in
kernel git repository and on Coccinelle web page), as they can eat
whole memory (12 GB RAM + SWAP) and/or appear to be hanging after a
few hours.
I am also new to coccinelle, and saw this issue. If I compile 3.2-ish
kernel with coccinelle check - the compilation dies. I also saw that
coccinelle works forewer with some files in the kernel.
Anyway, to work this around, I run spatch with -timeout 120.
Yes, good point. Still if there is some file of interest and some rule on
which it times out, please let me know.
I know that in at least some kernels there were some files with enormous
array initializers that Coccinelle had trouble parsing. But running such
files on Coccinelle is not useful either.
The best thing to do is use the timeout, and then look through your
standard output for EXN followed by Timeout and see if you care about
running the given semantic patch on any of those files.
julia
_______________________________________________
Cocci mailing list
[email protected]
http://lists.diku.dk/mailman/listinfo/cocci
(Web access from inside DIKUs LAN only)
