--- layout: fc_discuss_archives title: Message 65 from Frama-C-discuss on January 2014 ---
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Frama-c-discuss] [PROVENANCE INTERNET] Re: Frama-C: Detecting unreachable code?



Or, for toy examples like this, try pathcrawler-online.com
Click on 'Test your code', upload the attached file and test function
main, file reachable.c with default parameters and look at the
'coverage' tab of the result summary to see that the branch is not
covered or the 'Path' tab to see that all paths to this branch are
infeasible
Nicky

On 23/01/2014 10:07, Nicky Williams wrote:
> It's not open-source but the executbale files are available under
> certain conditions.
> Nicky
>
> On 23/01/2014 10:03, Nicholas Mc Guire wrote:
>> On Thu, 23 Jan 2014, Nicky Williams wrote:
>>
>>>    Of course, static analysis can only detect unreachable code.
>>>    To be sure that THERE IS NO unreachable code you need to do path testing,
>>>    eg. with the pathcrawler plugin (and to achieve full coverage with no
>>>    timeouts).
>> would be nice - but as far as I know that is a commercial plugin and
>> not available in any open-source implementation - pleas correct me if I'm wrong.
>>
>> thx!
>> hofrat
>>
>> _______________________________________________
>> Frama-c-discuss mailing list
>> Frama-c-discuss at lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/frama-c-discuss
>>
>
> _______________________________________________
> Frama-c-discuss mailing list
> Frama-c-discuss at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/frama-c-discuss
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: reachable.zip
Type: application/zip
Size: 215 bytes
Desc: not available
URL: <http://lists.gforge.inria.fr/pipermail/frama-c-discuss/attachments/20140123/6649eeb1/attachment.zip>