Replies: 1 comment
-
|
Wasmer 2, 3, and 4 are not maintained anymore: is there any way we can help make the latest version an option for you to use? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I am using Wasmer and have some code that calls
wasmer::Module::deserializeon bytes that I obtain in the following way:I recently upgraded from Wasmer 1 to 2, and after updating the API calls
deserializestarted to panic withcorrupted binary: misaligned metadata.Something strange that I noticed is that a well-crafted
println!()invocation before and afterdeserializemakes the problem go away. However, if this works for printing strings X and Y, it does not work when there is even the slightest change to X or Y.Does anyone have any clues as to why this may happen? Thank you! As a quick note, someone seems to be having a similar problem in this issue, but unfortunately the suggested fix of upgrading to Wasmer 3 is not an option for me.
Beta Was this translation helpful? Give feedback.
All reactions