> > It is possible that it is just very slow. When there are many nested
> > loops with many nested conditionals, then it is following all of the
> > control-flow paths, which can take a lot of time.
>
> Perhaps in such cases spatch could output a "spinner" showing it's still
> working and (slowly) making progress (something like the wget progress
> bar?)
I guess it could, but I'm not sure it would be so useful. Most of the
time when it doesn't return a result in a reasonable amount of time it
will actually never return a result. Even though it is doing work, and
even making progress, the amount of information it is building up will
cause it never to return.
There is an option -timeout n where n is a number of seconds that you may
find useful. Something between 60 and 120 usually gets you all of the
answers you are likely to get in practice.
> > You can use the options
> > -no_loops and -no_gotos which makes it not follow paths through loops or
> > gotos. This is not safe in general, but it should be ok for what is to be
> > done here.
>
> Right, but I wouldn't really want to be telling an analysis tool to
> ignore major features of a language. Seems like a bad idea in my
> opinion.
Indeed, it is only useful if you really understand what you want the tool
to do in the given case. In this case, you don't really care about the
paths from the start of the { to the continue, you just want the continue
to appear at the end. So at least following loops does not seem very
productive.
julia
_______________________________________________
Cocci mailing list
[email protected]
http://lists.diku.dk/mailman/listinfo/cocci
(Web access from inside DIKUs LAN only)
