-
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
runtime: bad pointer in frame github.com/konsorten/go-windows-terminal-sequences.EnableVirtualTerminalProcessing #1112
Comments
I'm seeing this too. It seems like v1.1.1 (bcd833d) is the most recent release that does not cause the error. |
I'm seeing this too. |
I'm seeing this also. |
Using Go 1.13 instead of 1.14 solves the problem. Environment: Windows 10 1909 Build 18363.720 Something has changed or there is a bug in the Go 1.14 stack management. |
I do not have any available windows environment to work on that. |
这个问题真的恶心到我了 ,浪费了两天时间在这个上面了 终于解决了 ,thanks very much |
I think the issue is related to this package https://github.com/konsorten/go-windows-terminal-sequences and go 1.14 |
You are right, the issue may caused by konsorten/go-windows-terminal-sequences package. Actually, has a issue created https://github.com/konsorten/go-windows-terminal-sequences/issues/4. |
I ran into this after adding a call to logrus.SetLevel. If I set the level using logrus.SetLevel, then subsequent logging calls result in a panic. If I remove the call to logrus.SetLevel, then the panic goes away. It does not seem to matter what level I set it to, just that I've set it at all... EDIT: in hindsight, it's pretty temperamental, and removing this SetLevel call does not always seem to work. |
EDIT: @dirty49374 proposed a fix which works. I confirmed that is now working for the example above. |
Confirmed to be fixed in https://github.com/konsorten/go-windows-terminal-sequences/releases/tag/v1.0.3 |
so we just need to update our dependencies to have the fix then |
@dgsb should wait logrus release new version to include go-windows-terminal-sequences patch version |
Thanks for the fix @fkollmann 👍 |
The following code snippet doesn't work on Windows 10, but works on macOS and Linux.
The text was updated successfully, but these errors were encountered: