Skip to content
This repository has been archived by the owner on Jun 7, 2022. It is now read-only.

Stack runs out when running a WASI executable on AArch64 #1

Open
igrep opened this issue Apr 15, 2020 · 2 comments
Open

Stack runs out when running a WASI executable on AArch64 #1

igrep opened this issue Apr 15, 2020 · 2 comments

Comments

@igrep
Copy link
Member

igrep commented Apr 15, 2020

The (incomplete) feature to run a WASI executable has never worked on AArch64 due to a stack overflow error.
I suspected this was a bug of wasmer at first, but learned this is caused by my code after investigating.
It seems that I created too many closures. They seem to consume stack as much as their internal local variables.

@igrep
Copy link
Member Author

igrep commented Apr 15, 2020

This bug is the one I refer in wasmerio/wasmer#1292 (comment)

@igrep
Copy link
Member Author

igrep commented Apr 16, 2020

I've found a much smaller example to reproduce the problem, thanks to wasmerio/wasmer#1379.
So now I think this can be a problem of wasmer because the example is too simple to be smaller.
Seems there's a known issue similar to this: https://stackoverflow.com/questions/27223005/unable-to-make-jni-call-from-c-to-java-in-android-lollipop-using-jni https://issuetracker.google.com/issues/37035211. Sorry.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant