-
-
Notifications
You must be signed in to change notification settings - Fork 367
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
yay segmentation violation: signal arrived during cgo execution #2536
Labels
Comments
I got a similar segfault (also looks similar to #2427), dump below: Details
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I update my Arch laptop every morning using
yay
and have been doing so for years. A couple of weeks ago I experienced a yay crash but just ran it immediately again and it worked fine. Today it crashed again so thought I should raise an issue about it. Version isyay v12.4.2 - libalpm v15.0.0
. Here is the output:I just ran it immediately again and it ran fine so this bug is not reproducible.
The text was updated successfully, but these errors were encountered: