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] WP and Allocations
- Subject: [Frama-c-discuss] WP and Allocations
- From: hirohito at cock.li (Emperor Hirohito)
- Date: Sun, 16 Feb 2020 01:49:02 -0600
I'm using Frama-C 20.0, alt-ergo 2.3.0, why3 1.2.1. Is there any reasonable way to deal with dynamic allocation with ACSL and WP? Here's a small sample program: > #include <stdlib.h> > > int > main(void) > { > char *p = malloc(10); > if (!p) > return 1; > //@ assert \valid(p); > return 0; > } When I run `frama-c -wp [filename]`, none of the provers are able to prove the assertion, while running `frama-c -eva [filename]` says that it's valid.
- Follow-Ups:
- [Frama-c-discuss] WP and Allocations
- From: loic.correnson at cea.fr (Loïc Correnson)
- [Frama-c-discuss] WP and Allocations
- Prev by Date: [Frama-c-discuss] Berlin software verification meetup 2020-02-26
- Next by Date: [Frama-c-discuss] WP and Allocations
- Previous by thread: [Frama-c-discuss] Berlin software verification meetup 2020-02-26
- Next by thread: [Frama-c-discuss] WP and Allocations
- Index(es):