mh4ck-Thales wrote: > I'd be happy to keep chatting about this if you're interested in exploring > that path further, now or in the future. I also don't want to necessarily > push you towards the GDB remote protocol. For languages like C++, Rust, > Swift, or really anything targeting LLVM/supported by LLDB, I strongly > believe that going with the GDB remote protocol is the best and easiest way > to support debugging, but I also totally acknowledge that the trade-offs may > be different for Wasmtime. That said, they also don't necessarily need to be > mutually exclusive.
I agree that the GDB remote protocol is the best / easiest way to debug everything supported by LLVM / that isn't interpreted in some way. Regarding the interpreted languages, I'd say that there is also a use for this king of debugging for allowing runtime developers to debug their runtime when compiled to Wasm. Most issues in an interpreted code that are not Wasm-related can be debugged on the language's runtime directly without going through Wasm, and Wasm-related bugs will often need access to the runtime as the bug being Wasm-specific may have something to do with the runtime. https://github.com/llvm/llvm-project/pull/150143 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
