We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If we call m3_Call / m3_CallVL / m3_CallArgv and Start-function not executed, then checkStartFunction is executing (here: https://github.com/wasm3/wasm3/blob/main/source/m3_env.c#L907), but arguments for called function is written to the stack above (here: https://github.com/wasm3/wasm3/blob/main/source/m3_env.c#L892) and after executing checkStartFunction the stack no longer contains arguments for called functions.
m3_Call
m3_CallVL
m3_CallArgv
Start
checkStartFunction
The text was updated successfully, but these errors were encountered:
fix for [issues#363](wasm3#363)
85ab2c6
issues#363
Sorry, something went wrong.
6e80fb1
m3_Call*-functions fix (#364)
7dd43c1
* fix for [issues#363](#363) * minor
Merged
No branches or pull requests
If we call
m3_Call
/m3_CallVL
/m3_CallArgv
andStart
-function not executed,then
checkStartFunction
is executing (here: https://github.com/wasm3/wasm3/blob/main/source/m3_env.c#L907),but arguments for called function is written to the stack above (here: https://github.com/wasm3/wasm3/blob/main/source/m3_env.c#L892)
and after executing
checkStartFunction
the stack no longer contains arguments for called functions.The text was updated successfully, but these errors were encountered: