-
Notifications
You must be signed in to change notification settings - Fork 446
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
segfault at 4.15.0-rc1 #6518
Comments
I will attempt to minimize the example next week. I thought the people managing the 4.15 release may want to see this asap. |
The segfault occurs in
|
This minimizes to
which exits with 139 under |
The orginally reported issue, however really is new to |
Ah, I'm an idiot, I've already encountered exactly this problem before in leanprover-community/aesop#182, and @JLimperg has fixed it in leanprover-community/aesop#183. Hence a solution is to use the
(Alternatively the |
(Please reopen, or ping me, if this solution won't suffice.) |
Prerequisites
Please put an X between the brackets as you perform the following steps:
https://github.com/leanprover/lean4/issues
There is Segfault in a complex test case #6332 but it is not at 4.15.
Avoid dependencies to Mathlib or Batteries.
https://live.lean-lang.org/#project=lean-nightly
(You can also use the settings there to switch to “Lean nightly”)
Description
[Clear and concise description of the issue]
Running
lake build && lake exe tensorlib
results in a segfault at 4.15.0-rc1 but is fine at 4.14.0.Context
[Broader context that the issue occurred in. If there was any prior discussion on the Lean Zulip, link it here as well.]
Steps to Reproduce
sm/segfault-at-4.15.0-rc1
branch: https://github.com/leanprover/TensorLib/tree/sm/segfault-at-4.15.0-rc1Expected behavior:
0 exit code
Actual behavior:
segfault
Versions
[Output of
#version
or#eval Lean.versionString
]4.15.0-rc1
[OS version, if not using live.lean-lang.org.]
OSX 14.7.1
Impact
Add 👍 to issues you consider important. If others are impacted by this issue, please ask them to add 👍 to it.
The text was updated successfully, but these errors were encountered: