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

Support mapping source paths in backtraces #8760

Open
tschneidereit opened this issue Jun 8, 2024 · 0 comments
Open

Support mapping source paths in backtraces #8760

tschneidereit opened this issue Jun 8, 2024 · 0 comments
Labels
enhancement wasmtime:debugging Issues related to debugging of JIT'ed code

Comments

@tschneidereit
Copy link
Member

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

@tschneidereit tschneidereit added enhancement wasmtime:debugging Issues related to debugging of JIT'ed code labels Jun 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement wasmtime:debugging Issues related to debugging of JIT'ed code
Projects
None yet
Development

No branches or pull requests

1 participant