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

Results of wtmaps look odd? #7

Open
kripken opened this issue Nov 28, 2019 · 0 comments
Open

Results of wtmaps look odd? #7

kripken opened this issue Nov 28, 2019 · 0 comments

Comments

@kripken
Copy link

kripken commented Nov 28, 2019

The attached testcase has these files:

  • emcc-0-base.wasm - initial wasm file
  • emcc-1-wtmaps.map - identity map
  • emcc-2-wasm-emscripten-finalize.wasm - output of the binaryen wasm-emscripten-finalize tool
  • emcc-3-output_map.map - the output source map from that tool
  • emcc-4-wasm-emscripten-finalize.wtmapped.wasm - the modified wasm after wtmaps ran, updating the debug info

The final updated file looks odd to me, but maybe I'm not looking at it right?

Attached is a screenshot that compares the 3 wasm files. The emcc-2 looks basically like emcc-0, which actually is surprising because the files are not identical, so I would have guessed the movement should have broken things? But both look ok, the source code makes sense for the wasm code.

But then emcc-4 looks odd, like something may have gone wrong?

mapping

emscripten_temp.zip

edit: to complete the STR, here is the command to get the final wasm from the previous files:

$ wdwarf-cp emcc-0-base.wasm -o out.wasm -m emcc-3-output_map.map -w emcc-2-wasm-emscripten-finalize.wasm 
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