I’m also in favour of keeping the GUI around. It’s not perfect, but at least in
a usable state and not a huge maintenance burden from what I can see.
- Raphael
> On 25. Aug 2019, at 02:02, Greg Clayton via lldb-dev
> wrote:
>
> I know many people use it. They tend to drop in and use it, and t
Hi there,
I am working on a project which involves compiling C++ source file to
Webassembly byte code file with LLVM. The LLVM works well and can generate
wasm byte code file with DWARF debug sections like .debug_line. I can run
the generated wasm file with my wasm virtual machine. However I find
I’m not sure I understand what the question is. Do you want that LLDB attachs
to the wasm program running inside your VM and then debug the wasm program via
LLDB? Or that LLDB can run the wasm module itself like an executable and then
run it/step through it/inspect it/etc.?
Cheers,
- Raphael
>
+lldb-dev
> On 26. Aug 2019, at 12:57, Raphael “Teemperor” Isemann
> wrote:
>
> If I understand correctly your VM is your own custom wasm interpreter/JIT? If
> yes, then I don’t think it is realistic that LLDB can ever support it out of
> the box. But you can write a LLDB plugin that calls yo
On Monday August 26 2019 11:18:28 Raphael “Teemperor” Isemann via lldb-dev
wrote:
>> On 25. Aug 2019, at 02:02, Greg Clayton via lldb-dev
>> wrote:
>>
>> I know many people use it.
Count me among those who didn't even know it existed - is it even packaged in
any of the official LLVM (.deb) p
The GUI is built into lldb, it is not a separate entity.
Jim
> On Aug 26, 2019, at 12:39 PM, René J.V. Bertin via lldb-dev
> wrote:
>
> On Monday August 26 2019 11:18:28 Raphael “Teemperor” Isemann via lldb-dev
> wrote:
>
>>> On 25. Aug 2019, at 02:02, Greg Clayton via lldb-dev
>>> wrote:
On 20190826 21:41, Jim Ingham wrote:
The GUI is built into lldb, it is not a separate entity.
Oh, right, so a "AUI" or "CUI" rather than something properly graphical. Sorry,
not very useful to me.
R.
___
lldb-dev m
Hi Raphael,
Thanks for your recommendation. How about the very first step which
enables LLDB to recognize the wasm bytecode via commands like "lldb
my.wasm" or "file my.wasm" inside lldb? And IMHO the second step is to
enable LLDB to recognize the dwarf sections embedded in wasm bytecode
file. Do
