Skip to content
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.

Sign up for GitHub

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

Jump to bottom

BUG: parsing running wasm file causing crash #174

Open
mim-ll opened this issue Apr 19, 2020 · 2 comments
Open

BUG: parsing running wasm file causing crash #174

mim-ll opened this issue Apr 19, 2020 · 2 comments

Comments

@mim-ll
Copy link

mim-ll commented Apr 19, 2020 •
edited
Loading

:eosio::vm::registered_host_functions<decltype(nullptr)>::operator()<eosio::vm::execution_context<decltype(nullptr)> >(decltype(nullptr)*, eosio::vm::execution_context<decltype(nullptr)>&, unsigned int) parsing running wasm file causing crash
@mim-ll mim-ll closed this as completed Apr 19, 2020
@mim-ll mim-ll reopened this Apr 19, 2020
@mim-ll
Copy link
Author

mim-ll commented Apr 19, 2020

detail.zip

@mim-ll mim-ll changed the title BUG:eosio::vm::registered_host_functions<decltype(nullptr)>::operator()<eosio::vm::execution_context<decltype(nullptr)> >(decltype(nullptr)*, eosio::vm::execution_context<decltype(nullptr)>&, unsigned int) parsing running wasm file causing crash BUG: parsing running wasm file causing crash Apr 19, 2020
@swatanabe-b1
Copy link
Contributor

Assuming that you are running eos-vm-interp, the problem is that this program does not handle imports at all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@swatanabe-b1 @mim-ll