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.

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

mean-squares-versor-registration example backtrace on WASI exit #794

Open
thewtex opened this issue Mar 16, 2023 · 0 comments
Open

mean-squares-versor-registration example backtrace on WASI exit #794

thewtex opened this issue Mar 16, 2023 · 0 comments

Comments

@thewtex
Copy link
Member

thewtex commented Mar 16, 2023

With a debug build:

npm run build:wasi:debug

and test,

npm run test:wasi

the pipeline creates the result successfully, but on destructor cleanup:

1: Caused by:
1:     0: failed to invoke command default
1:     1: error while executing at wasm backtrace:
1:            0: 0xab50a - <unknown>!dlfree
1:            1: 0xab410 - <unknown>!free
1:            2: 0xa95a3 - <unknown>!operator delete(void*)
1:            3: 0x258b66 - <unknown>!itk::LightObject::~LightObject()
1:            4: 0x23f139 - <unknown>!itk::LightObject::UnRegister() const
1:            5: 0x269bda - <unknown>!__cxx_global_array_dtor.58
1:            6: 0xadc5a - <unknown>!__funcs_on_exit
1:            7: 0xadbd8 - <unknown>!__wasm_call_dtors
1:            8: 0x29be61 - <unknown>!itk_wasm_delayed_exit
1:            9: 0x29beea - <unknown>!_start
1:        note: using the `WASMTIME_BACKTRACE_DETAILS=1` environment variable may show more debugging information
1:     2: wasm trap: out of bounds memory access
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant