Wasmtime GitHub notifications bot (Mar 04 2020 at 14:26): Wasmtime GitHub notifications bot (Mar 04 2020 at 14:26):yurydelendik commented on Issue #1040:
For other wasm-using users of Cranelift, that requires depending on wasmtime-debug and wasmtime-environ. Is that the way to go?
For non-wasm users of Cranelift, I don't think the wasmtime-debug machinery applies so much
At the very least, I'd like to at least look into upstreaming the DWARF translation into cranelift-wasm
Earlier, we were trying to decide if the "debug" crate shall be in cranelift or wasmtime project, and norrowed a scope to the wasmtime only. Since it is a single repository now, we have a choice to generalize wasmtime-debug crate and make it available for non-wasm users.
it specifically references VMContext
The wasmtime-debug crate is using cranelift data to generate DWARF sections. The VMContext is coming into play only for DWARF expression and can be changed to use some other Instance/State/Context abstraction or none.
@iximeow FWIW, as stated, the original issue is vague and it turned into set of ideas without a acceptable plan. It is correct that the existing solution provides a way to debug cratelift generated code for wasm users due to the wasmtime location. Let's file a separate issues for the deficiencies of the current implementation. Or is it preferable to keep this issue opened for that?
Last updated: Dec 23 2024 at 13:07 UTC