We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
in this (https://groups.google.com/forum/#!topic/cprover-support/rQrlv7NY79A)[thread] a user posted a Verilog file for which apparently properties can only be specified on the command line, properties in the file give
file or1200_if.v line 222: syntax error before ' ( ' PARSING ERROR
version 4.4 fails even when the property is specified on the command line
Parsing or1200_if.v Converting Type-checking Verilog::or1200_if Type-checking Verilog::main --- begin invariant violation report --- Invariant check failed File ../../lib/cbmc/src/util/message.h function get_message_handler line 129 Reason: message handler is setBacktrace: Backtrace ebmc() [0x46e191] ebmc() [0x46e706] ebmc() [0x42ccbd] ebmc() [0x42cc8b] ebmc() [0x42a868] ebmc() [0x5f3ea4] ebmc() [0x42add0] ebmc() [0x4267de] ebmc() [0x4299ba] ebmc() [0x4441ad] ebmc() [0x417ca2] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f25b62b6830] ebmc() [0x40c2a9] --- end invariant violation report --- fish: “ebmc or1200_if.v --module main…” terminated by signal SIGABRT (Abort)
which works with 4.2
The text was updated successfully, but these errors were encountered:
#31 solves the invariant violation
Sorry, something went wrong.
This may be fixed by #264
I would be grateful if you could confirm whether #264 (now merged) has fixed this.
No branches or pull requests
in this (https://groups.google.com/forum/#!topic/cprover-support/rQrlv7NY79A)[thread] a user posted a Verilog file for which apparently properties can only be specified on the command line, properties in the file give
version 4.4 fails even when the property is specified on the command line
which works with 4.2
The text was updated successfully, but these errors were encountered: