Frama-C-discuss mailing list archives
This page gathers the archives of the old Frama-C-discuss archives, that was hosted by Inria's gforge before its demise at the end of 2020. To search for mails newer than September 2020, please visit the page of the new mailing list on Renater.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Frama-c-discuss] [PROVENANCE INTERNET] Re: Frama-C: Detecting unreachable code?
- Subject: [Frama-c-discuss] [PROVENANCE INTERNET] Re: Frama-C: Detecting unreachable code?
- From: nicky.williams at cea.fr (Nicky Williams)
- Date: Thu, 23 Jan 2014 10:24:47 +0100
- In-reply-to: <18959_1390468051_52E0DBD3_18959_19153_1_52E0DBBB.9080202@cea.fr>
- References: <B517F47C2F6D914AA8121201F9EBEE6701C7660449A7@Mail1.FCMD.local> <52E0C26F.2000605@linux-france.org> <20140123082550.GA7256@opentech.at> <CAOH62JhyfqOmKmw5iKjx1CSifK2X6ajxZBxd--h4_nK-3OxmrA@mail.gmail.com> <52E0D85C.3060504@cea.fr> <20140123090356.GA22094@opentech.at> <18959_1390468051_52E0DBD3_18959_19153_1_52E0DBBB.9080202@cea.fr>
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>
- References:
- [Frama-c-discuss] Frama-C: Detecting unreachable code?
- From: dganesan at fc-md.umd.edu (Dharmalingam Ganesan)
- [Frama-c-discuss] Frama-C: Detecting unreachable code?
- From: dmentre at linux-france.org (David MENTRE)
- [Frama-c-discuss] Frama-C: Detecting unreachable code?
- From: der.herr at hofr.at (Nicholas Mc Guire)
- [Frama-c-discuss] Frama-C: Detecting unreachable code?
- From: pascal.cuoq at gmail.com (Pascal Cuoq)
- [Frama-c-discuss] Frama-C: Detecting unreachable code?
- From: nicky.williams at cea.fr (Nicky Williams)
- [Frama-c-discuss] Frama-C: Detecting unreachable code?
- From: der.herr at hofr.at (Nicholas Mc Guire)
- [Frama-c-discuss] Frama-C: Detecting unreachable code?
- Prev by Date: [Frama-c-discuss] Frama-C: Detecting unreachable code?
- Next by Date: [Frama-c-discuss] Frama-C: Detecting unreachable code?
- Previous by thread: [Frama-c-discuss] Frama-C: Detecting unreachable code?
- Next by thread: [Frama-c-discuss] Frama-C: Detecting unreachable code?
- Index(es):