-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
wasmtime panic with .NET 9.0 WASI wasm file #8904
Labels
bug
Incorrect behavior in the current implementation that needs fixing
Comments
CryZe
added
the
bug
Incorrect behavior in the current implementation that needs fixing
label
Jul 5, 2024
alexcrichton
added a commit
to alexcrichton/wasmtime
that referenced
this issue
Jul 8, 2024
I'm not entirely sure what causes this but Wasmtime shouldn't panic with invalid DWARF. In general (bytecodealliance#5537) Wasmtime's support for DWARF needs to be rewritten, but in the meantime let's play whack-a-mole with panics and try to paper over issues. Closes bytecodealliance#8884 Closes bytecodealliance#8904
alexcrichton
added a commit
to alexcrichton/wasmtime
that referenced
this issue
Jul 9, 2024
I'm not entirely sure what causes this but Wasmtime shouldn't panic with invalid DWARF. In general (bytecodealliance#5537) Wasmtime's support for DWARF needs to be rewritten, but in the meantime let's play whack-a-mole with panics and try to paper over issues. Closes bytecodealliance#8884 Closes bytecodealliance#8904
fitzgen
added a commit
that referenced
this issue
Jul 9, 2024
* Add custom-pages-sizes to CLI flags (#8917) * Update dependency on `wit-bindgen` (#8911) * Update dependency on `wit-bindgen` Updating to the latest released version. * Add vets * Fix build of test-programs * Fix panic with invalid DWARF file indices (#8913) I'm not entirely sure what causes this but Wasmtime shouldn't panic with invalid DWARF. In general (#5537) Wasmtime's support for DWARF needs to be rewritten, but in the meantime let's play whack-a-mole with panics and try to paper over issues. Closes #8884 Closes #8904 * Wasmtime: Pop GC LIFO roots even when there is no GC heap (#8899) * Wasmtime: Pop GC LIFO roots even when there is no GC heap We can create and root `i31ref`s without ever allocating a GC heap for the store, so we can't guard popping LIFO roots on the presence of a GC heap or else we risk unbounded growth of the LIFO root set. * Fix build with the gc feature disabled --------- Co-authored-by: Nick Fitzgerald <fitzgen@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Test Case
net9_debug_crash.zip
Steps to Reproduce
Configure the engine the following way:
Expected Results
It compiles the module.
Actual Results
It panics:
Versions and Environment
Wasmtime version or commit: 22.0.0
Operating system: Windows 11
Architecture: x86_64
The text was updated successfully, but these errors were encountered: