How do I trace such a bug on wasmJs browser sub ta...
# webassembly
a
How do I trace such a bug on wasmJs browser sub target?
Copy code
WebAssembly.instantiateStreaming(): struct.new[2] expected type (ref null 17), found ref.null of type nullref @+9286076
CompileError: WebAssembly.instantiateStreaming(): struct.new[2] expected type (ref null 17), found ref.null of type nullref @+9286076
The console doesn't print anything useful as well
i
Hi, is it possible to share sources produce this issue?
a
The project is too big to share, and it is also private. But if you can help me on how to debug this, so that I can try to create at least minimal reproducer. Other than that, it is really hard for me to debug this
i
You can try to install IJ Hexana plugin. Open non-optimised (in build/compileSync/wasmJs/main/developmentExecutable/...) .wasm file with it and in WAT tab and find the offset to see, what part wasm file is broken.
The offset should be from that file, of course 🙂
But
expected type (ref null 17), found ref.null of type nullref
looks a bit weird...expecting
null 17
but found
nullref
which is bottom type...
a
let me try to do so!