-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
fatal: morestack on g0 #12021
Comments
Please provide some steps to reproduce the issue. It's hard to understand where the issue comes from without an example. From reading golang/go#62130 they seem to have a clear grasp of what's causing this.
I don't know exactly how FFI works under the hood, but it must allocate space for the stack somewhere for executing the given function. It sounds like Go assumes that the stack will never change. Thus different FFI calls with execution of |
Sure here are some steps to reproduce:
It will likely stop at "VerifyAccount" test with that error. Also if you just run that single test it will work, but running all of them it will not. Maybe related which what you said? Btw this only happens on Apple Sillicon, I was not able to reproduce it on Ubuntu 22 (but maybe because my go version might be older? Let me update it on ubuntu to check if it will happen as well) |
Yep, I've updated go, rebuilt the lib, and could not reproduce it on Ubuntu 22 with PHP 8.2.9. I can only reproduce it on Apple Sillicon using the same PHP and GO versions |
I guess it is worth taking a look in this issue to get more clarification: dunglas/frankenphp#171 (comment) |
Note that we cannot reproduce our issue on Apple Silicon, only AMD64. So they may be related, but in different ways. |
I guess it could really be as he said golang/go#62130 (comment) |
Description
I'm getting this error when running a test that uses FFI to execute a go lib.
It is probably related to this issue: golang/go#62130
Not sure where the problem lies php or go
Resulted in this output:
PHP Version
PHP 8.2.9
Operating System
macOS 13.4
The text was updated successfully, but these errors were encountered: