-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Crash when running example.ml (Ocaml) #5517
Comments
I can't address bugs in downstream versions of z3 |
I tried the OCaml example using the latest Z3 and get the same error:
Do you think the |
For reference, I built z3 this way, following the build and install instructions in the opam file for 4.8.11 by @c-cube:
There was an issue earlier with |
To my opinion it is irrelevant. It is just saying that there was no such folder. The package is linked statically, and there are no extra dependencies, and it loads without any linker errors, so it looks good to me. And the message is likely coming from the C++ to C boundary from an escaping exception. Have you tried this example on a Linux machine? |
For your information, I tried this on a Linux machine and an old version of z3 (4.8.9) and the example works perfectly fine. |
I will try on Linux later today, but this is certainly an issue on Mac as reported by OP and confirmed with my report. |
So I may be doing something really stupid, but I can't seem to get
|
Z3 vs. z3? |
Wow, indeed that fixed it on Linux, but the official example at https://github.com/Z3Prover/z3/blob/master/examples/ml/README does have what I wrote above. While both Perhaps, the example doc needs to be fixed. @ivg answered it here: https://stackoverflow.com/a/50004273/1167061 |
I currently have z3.4.8.11 installed, and when running the example, I get this error:
We are building with dune:
and running using
the directory looks like this:
where example.ml is this file: https://github.com/Z3Prover/z3/blob/master/examples/ml/ml_example.ml
Note:
I am on macOS Big Sur (11.5.2)
The text was updated successfully, but these errors were encountered: