bytecodealliance / bytecodealliance/wasmtime
Support mapping source paths in backtraces
- Dominant language
- Rust
- Stars
- 18.6k
- Forks
- 1.8k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 126
Description
#### Feature
GDB and LLDB have facilities for mapping source paths to address situations in which code was compiled in a different location from where the source is located on the machine it's run/debugged on. It'd be great to support this for Wasmtime backtraces, too.
#### Benefit
Making debugging of code compiled elsewhere easier.
#### Implementation
I'm not sure where exactly the search/replace would happen that'd lead to changed output. What I imagine for the user experience is something like a new (repeatable) CLI argument along the lines of `-D source-map [path-prefix]::[path]`
#### Alternatives
Doing nothing
Contributor guide
Assessment
This issue has not been assessed yet.