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] trouble debugging assertions
- Subject: [Frama-c-discuss] trouble debugging assertions
- From: anne.pacalet at free.fr (Anne Pacalet)
- Date: Tue, 18 Aug 2015 08:57:43 +0200
- In-reply-to: <CAGSRWbiNW1JwsppB0D3=Cz5G-V95TrpetE5cC4XkMDNLBDyWVA@mail.gmail.com>
- References: <CAGSRWbiNW1JwsppB0D3=Cz5G-V95TrpetE5cC4XkMDNLBDyWVA@mail.gmail.com>
Hi Tim, Le 18/08/2015 08:44, Tim Newsham a écrit : > What is confusing me is that the assertion right after the call site is the > same (seems to me!) as the "ensures" clause of the implementation! So why > is the analyzer not drawing the connection? Is there something I can do to > help it out? I suspect that the states computed at the end of the function are merged before returning, so the assertion cannot be verified anymore on the merged state. Maybe you should try to use the option: -val-split-return auto or -val-split-return-function auth:full Hope this helps. Anne.
- Follow-Ups:
- [Frama-c-discuss] trouble debugging assertions
- From: tim.newsham at gmail.com (Tim Newsham)
- [Frama-c-discuss] trouble debugging assertions
- References:
- [Frama-c-discuss] trouble debugging assertions
- From: tim.newsham at gmail.com (Tim Newsham)
- [Frama-c-discuss] trouble debugging assertions
- Prev by Date: [Frama-c-discuss] trouble debugging assertions
- Next by Date: [Frama-c-discuss] trouble debugging assertions
- Previous by thread: [Frama-c-discuss] trouble debugging assertions
- Next by thread: [Frama-c-discuss] trouble debugging assertions
- Index(es):