Rick Bradley <rick / rickbradley.com> wrote in message news:<20020514044853.GK580 / negwo.eastcore.net>...
> A (highly) contrived fragmentary example showing why such a coverage
> tool (or any coverage tool which executes code modified by a simple
> automatic process) might cause problems:
> 
>     status = "unsafe"
>     system ("/bin/rm -rf /") if status != "unsafe"

ugg, that's a nasty example.

> This is something of an extreme, but less contrived cases can arise that
> can cause subtle problems.  $SAFE may not be the right solution either
> (since code is often intentionally unsafe).  The Halting Problem says
> that detecting harmful cases syntactically is likely to be an exercise
> in futility.

Do you have any links to more information about the issues in doing
coverage analysis?  What is The Halting Problem?

Thanks,

~ Patrick