emscripten-core / emscripten-core/emscripten

[wasm-split] Reconstruct production stackTrace

Open
#21,397 3 comments 0 reactions 1 assignee Claimed by @tlively View on GitHub
Dominant language
C++
Stars
27.6k
Forks
3.6k
Avg merge
1d 1h
Merged PRs (30d)
105

Description

Please include the following in your bug report:

**Version of emscripten/emsdk:**
```
emcc (Emscripten gcc/clang-like replacement + linker emulating GNU ld) 3.1.35 (a90c5abb489c516f59c0d16864d953d4bedd37da)
clang version 17.0.0 (https://github.com/llvm/llvm-project 6865cff8ea8b07d9f2385fd92cecb422404f0f35)
Target: wasm32-unknown-emscripten
Thread model: posix
InstalledDir: ~/emsdk/upstream/bin
```

For reconstructing production stack traces, we earlier used `.js.symbols` file which we get using `--emit-symbol-map` flag. That file had a map of function index to function name. With wasm-split we get `.wasm.symbols` file with `--symbolmap` flag. That file contains a map of function index to minified function names which are not meaningful for debugging purpose. Is there a way to get get actual function names like that in `.js.symbols` file from these minified function names?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.