-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Logrus crashes on terminal check #1275
Comments
I believe Apple has made security changes in Big Sur, and perhaps now applications are no longer allowed by default to make certain syscalls - e.g. this one to get terminal properties. |
I believe the golang.org/x/sys should be updated to version v0.0.0-20210817190340-bfb29a6856f2 when using go 1.17. The crash went away for me when I added to go.mod:
More info: Homebrew/homebrew-core#83413 Maybe the logrus go.mod should be updated? |
Thanks, this works |
- fix `go vet` error - fix build on Big Sur due to new security limits which impact logrus: sirupsen/logrus#1275
An easier solution that fixed it for me is upgrading the sys dependency: |
This same bug is affecting WTF: sirupsen/logrus#1275 Signed-off-by: Chris Cummer <chriscummer@me.com>
Thank you @machinae for suggesting this fix. It appears to have solved it for WTF. |
Older version of indirect golang.org/x/sys caused SIGSEGV on Go 1.17 on MacOS Big Sur See sirupsen/logrus#1275 Fixes #1836 Signed-off-by: Alexander Yastrebov <alexander.yastrebov@zalando.de>
Older version of indirect golang.org/x/sys caused SIGSEGV on Go 1.17 on MacOS Big Sur See sirupsen/logrus#1275 Fixes #1836 Signed-off-by: Alexander Yastrebov <alexander.yastrebov@zalando.de>
Hi,
We integrated logrus into our application but it crashes when running. We are using 1.8.1. It appears to be doing a terminal check that it's not running on app engine, and the crash occurs in a syscall. Here is the stack trace:
OS is MacOS Big Sur 11.5.2
Go version is 1.17
AMD64 arch
Any thoughts on what might be causing this?
The text was updated successfully, but these errors were encountered: