Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File "verifast1.ml", line 301, characters 23-29: Assertion failed #24

Closed
jameshfisher opened this issue Apr 24, 2016 · 2 comments
Closed

Comments

@jameshfisher
Copy link

I get this error when attempting to verify a file:

$ ~/Downloads/verifast-16.01/bin/verifast rb_msg_store.c
rb_msg_store.c
Fatal error: exception File "verifast1.ml", line 301, characters 23-29: Assertion failed

Comes from https://github.com/verifast/verifast/blob/master/src/verifast1.ml#L301 :

    | StructType sn -> failwith "Using a struct as a value is not yet supported."

Seeing the message in the source I was quickly able to fix the error. Until this feature is added, can we ensure that the failure message is shown to the end user?

Btw @btj long time no speak! Very glad to see you're still working on VeriFast. And it's great to see that it's finally open source! (Because I wouldn't have been able to move past this error otherwise :-) )

@btj
Copy link
Member

btj commented Apr 25, 2016

Hi James,

Yes, long time no speak :-) Glad to see you're still playing with VeriFast!

With respect to the issue: this was fixed by bec3035, post-release 16.01. I'll leave this issue open, though, as a reminder to produce a new release.

@jameshfisher
Copy link
Author

Ah, great! I should try building from source.

I picked up VeriFast again at the weekend because we have some C code which is important, optimized for hot path, and has a nice logical interface, which is ideal for verification. I did a little research and it seems VeriFast is still the premier tool for C verification. (I also looked at Frama-C, which by comparison seems complex and ad hoc.)

@btj btj closed this as completed Aug 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants