hardfist opened Issue #1953:
I following the instruction in this article https://hacks.mozilla.org/2019/09/debugging-webassembly-outside-of-the-browser/,
it works fine for gdb on macos and lldb on linux, but it does not works well for lldb on macos
I try the following ways, but all failed,
- codesign lldb
- build lldb using
-DLLDB_USE_SYSTEM_DEBUGSERVER=ON
can someone give me an example on how to debug on macOS using lldb
abrown labeled Issue #1953:
I following the instruction in this article https://hacks.mozilla.org/2019/09/debugging-webassembly-outside-of-the-browser/,
it works fine for gdb on macos and lldb on linux, but it does not works well for lldb on macos
I try the following ways, but all failed,
- codesign lldb
- build lldb using
-DLLDB_USE_SYSTEM_DEBUGSERVER=ON
can someone give me an example on how to debug on macOS using lldb
yurydelendik commented on Issue #1953:
it works fine for gdb on macos and lldb on linux
can someone give me an example on how to debug on macOS using lldbThe only difference between linux and macos is default state of "plugin.jit-loader.gdb.enable" settings. You can add
settings set plugin.jit-loader.gdb.enable on
to ".lldbinit" or beginning of the lldb session. This setting was added in lldb version 9. Other than that, linux and macosx behavior shall be almost identical.
yurydelendik edited a comment on Issue #1953:
it works fine for gdb on macos and lldb on linux
can someone give me an example on how to debug on macOS using lldbThe only difference between linux and macos is default state of "plugin.jit-loader.gdb.enable" settings. You can add
settings set plugin.jit-loader.gdb.enable on
to ".lldbinit" or beginning of the lldb session. This setting was added in lldb version 9 (see e.g. brew's one). Other than that, linux and macosx behavior shall be almost identical.
hardfist commented on Issue #1953:
it works fine for gdb on macos and lldb on linux
can someone give me an example on how to debug on macOS using lldbThe only difference between linux and macos is default state of "plugin.jit-loader.gdb.enable" settings. You can add
settings set plugin.jit-loader.gdb.enable on
to ".lldbinit" or beginning of the lldb session. This setting was added in lldb version 9 (see e.g. brew's one). Other than that, linux and macosx behavior shall be almost identical.Thank you, It works now, but it seems not working in vscode when using
https://github.com/vadimcn/vscode-lldb
plugin
hardfist edited a comment on Issue #1953:
it works fine for gdb on macos and lldb on linux
can someone give me an example on how to debug on macOS using lldbThe only difference between linux and macos is default state of "plugin.jit-loader.gdb.enable" settings. You can add
settings set plugin.jit-loader.gdb.enable on
to ".lldbinit" or beginning of the lldb session. This setting was added in lldb version 9 (see e.g. brew's one). Other than that, linux and macosx behavior shall be almost identical.Thank you, It works now, but it seems not working in vscode when using codelldb plugin
hardfist commented on Issue #1953:
oh, after setup
initCommands
, it works now
yurydelendik commented on Issue #1953:
Closing as resolved
yurydelendik closed Issue #1953:
I following the instruction in this article https://hacks.mozilla.org/2019/09/debugging-webassembly-outside-of-the-browser/,
it works fine for gdb on macos and lldb on linux, but it does not works well for lldb on macos
I try the following ways, but all failed,
- codesign lldb
- build lldb using
-DLLDB_USE_SYSTEM_DEBUGSERVER=ON
can someone give me an example on how to debug on macOS using lldb
Last updated: Dec 23 2024 at 12:05 UTC