mh4ck-Thales wrote:
This PR hasn't moved in months now, are we missing something? It would be nice
to have this merged so we can build upon this to bring more interest and
support from the Wasm community and push for an implementation of lldb servers
in various Wasm runtimes.
https://github.c
mh4ck-Thales wrote:
> On the other hand, as a managed language, I think most people won't need to
> read specific local/global of an instance, just like most of the JavaScript
> developer won't care about the value of a register in V8 during debugging,
> they just care about the value of their
mh4ck-Thales wrote:
> Hi @mh4ck-Thales this is caused by [#77949
> (comment)](https://github.com/llvm/llvm-project/pull/77949#discussion_r1463458728),
> currently we need to modify it manually.
Thanks! That did the trick for the breakpoint and disassembly problems. When
using `read register`
mh4ck-Thales wrote:
I already tried to use `register read` to access Wasm variables without
success. But it was the patch available
[here](https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/build-scripts/lldb_wasm.patch)
is part of WAMR, maybe this patch is different and will mak
mh4ck-Thales wrote:
@jimingham sorry if I wasn't clear. `frame var` and `target var` are commands
for viewing *language* local and global variables (be it C or another one).
They are indeed working with this patch. These commands are using the Wasm
linear memory, where most of the data about t
mh4ck-Thales wrote:
Seems like support for reading Wasm local and global variables is available in
your code, but I don't understand how can one effectively read these variables
from the lldb command line. Maybe adding commands to access these can be useful
?
https://github.com/llvm/llvm-proj
