bytecodealliance / bytecodealliance/wasmtime-dotnet
Debugging WASM module in .NET host
- Dominant language
- C#
- Stars
- 519
- Forks
- 67
- Avg merge
- 1h 7m
- Merged PRs (30d)
- 1
Description
Hello,
I've been using Wasmtime as the runtime of a little project of mine, a fantasy console inspired by early 2000s game consoles and running WASM-based games.
It's been working quite well, but I've hit a bit of a snag. I'm trying to find ways to improve the debugging experience - log message debugging isn't super ideal, I'd like to be able to breakpoint my Rust source code and step through it from VSCode.
So, I installed the CodeLLDB plugin, set up a launch.json which boots my fantasy console passing the WASM module it should load on start, and then set a breakpoint and... nothing happens. It just skips right past the breakpoint, which seems to never resolve and just stays greyed out.
I'm definitely compiling my WASM module in debug mode (even added "-g" to my RUSTFLAGS just to be sure), and in my .NET host I've made sure I'm using a configuration with the .WithDebugInfo(true) option.
I'm not sure if I've missed something here or if this isn't actually a supported case?
Running on Windows 64-bit, .NET 6.0. Any help would be appreciated!
EDIT: Oh. I see, JIT debugging in LLDB seems to still be unsupported on Windows. Does that mean I should be trying to use GDB from mingw-64 instead?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.