-
The following C program verifies:
```c
#include
#include
int main() {
int* ptr = (int*) malloc(sizeof(int)*1000000);
assert(ptr != NULL);
free(ptr);
}
```
However, `mallo…
-
-
-
**Issue by [luigiapetre](https://github.com/luigiapetre)**
_Tuesday Aug 21, 2018 at 10:12 GMT_
_Originally opened as https://github.com/luigiapetre/Formal-Methods-Courses/issues/30_
----
Cour…
-
### I've searched open & closed issues for similar requests
- [X] Yes
### Package name
frama-c
### Package homepage
https://frama-c.com/
### Languages
C
### How is this package…
-
Hello,
Thanks for headache! I've mentioned your project in the acknowledgment section of https://github.com/mbarbin/vcs but I take this opportunity to thank you directly for this tool!
I tried r…
-
Current syntax for `spec` requires user to retype function name and argument types. It's flexible, but tedious. Here's a proposal for not doing that.
Restriction on C syntax: should error (require …
-
This succeeds silently, I think it should give an error for this case and a warning for duplicate specs at all.
```
void f (int *res);
/*@ spec f(pointer res);
requires take x = Block(res);
…
-
(This is a question about a somewhat unintuitive behavior related to `opam pin`; sorry if it is already mentioned somewhere.)
One user of our opam package used a `opam pin --kind path ` to install …
-
How does the option `-wp-gen` work in Frama-C 20?
Specifically, I would like to obtain the proof obligations for `cvc4` (or the other supported provers) of the example `find.c` below.
I tried
```
…