-
Notifications
You must be signed in to change notification settings - Fork 33
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
unable to start PVS 7.1.x on OSX #80
Comments
Hey Joe,
Hope you're doing well.
Could you type "bac" at the "0]" prompt, and send me the resulting
backtrace?
Thanks,
Sam
Joseph Kiniry ***@***.***> wrote:
… Hey Sam,
I wanted to migrate to PVS 7 today, but the pre-built sbcl binary fails with the following messages in
*pvs*, so the front-end comes crashing down.
Starting pvs-sbclisp --noinform --no-userinit ...
Setting tmp dir to value of environment variable TMPDIR:
/var/folders/xs/qk526nsd6hg6vjg9njg3fnc80000gp/T/
debugger invoked on a TYPE-ERROR:
The value (:HOME ".cache" "common-lisp" :IMPLEMENTATION)
is not of type
(OR (VECTOR CHARACTER) (VECTOR NIL) BASE-STRING PATHNAME FILE-STREAM).
Type HELP for debugger help, or (SB-EXT:EXIT) to exit from SBCL.
(no restarts: If you didn't do this on purpose, please report it as a bug.)
(PATHNAME-DIRECTORY (:HOME ".cache" "common-lisp" :IMPLEMENTATION)) [tl,external]
0]
0]
This failure happens even when I move my ~/.cache elsewhere.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Hi Sam, Hope you are doing well too. Perhaps I'll even get to come down and see you all before the end of this year. 🤞 Here is more context. I ran the binary directly as the
|
Has anyone found a solution to this problem? I experience exactly the same, the buffer
That directory is clearly writable. This problem occurs with pvs and sbcl from here (github) and sbcl compiled with the sbcl binary from homebrew, both on Intel and on ARM macs. |
Hey Sam,
I wanted to migrate to PVS 7 today, but the pre-built sbcl binary fails with the following messages in
*pvs*
, so the front-end comes crashing down.This failure happens even when I move my
~/.cache
elsewhere.The text was updated successfully, but these errors were encountered: