Repository navigation
wasm debug crash in lldb on MacOSX #2817
Description
Activity
Your bug report is not very clear, I'm afraid. What does "debug crash" mean? I see "process exited with status -1", is that what you mean? Can you elaborate how that constitutes a crash?
More generally, I can't get
lldb -- nodeto not exit -1 on macOS (10.15.5)Your bug report is not very clear, I'm afraid. What does "debug crash" mean? I see "process exited with status -1", is that what you mean? Can you elaborate how that constitutes a crash?
yeah, I mean
process exited with status -1and the program not working as expectedI can't reproduce on macos 10.14.6 with lldb 1001.0.13.3. The
process exited with status -1thing is probably something specific to macos 10.15 or the version of lldb you and @devsnek are using.the program not working as expected
What do you mean? Is "the program" node or lldb and what specifically isn't working as expected?
I can't reproduce on macos 10.14.6 with lldb 1001.0.13.3. The
process exited with status -1thing is probably something specific to macos 10.15 or the version of lldb you and @devsnek are using.the program not working as expected
What do you mean? Is "the program" node or lldb and what specifically isn't working as expected?
it should print "res: 5", but as you see in the screenshot, it just exit with exitcode -1 ,and print nothing
sudo DevToolsSecurity -enable
failed again
I can't repro anymore after enabling developer mode.
I can't repro anymore after enabling developer mode.
it works when using the latest node I build with source now , but the dwarf debug seems not working
I've moved this to nodejs/help because it's likely a toolchain issue, almost certainly not an issue with node itself.
did you
(lldb) settings set plugin.jit-loader.gdb.enable on?
did you
(lldb) settings set plugin.jit-loader.gdb.enable on?
yes, I set it on .lldbinit
I am asking because that made breakpoints of
lldb-10work for me, underwasmtime-0.17.I am asking because that made breakpoints of
lldb-10work for me, underwasmtime-0.17.yes , it works well for wasmtime but not nodejs
@bnoordhuis I can debug node using lldb my built node(nodejs/node#34340) , but it seems that
node still doesn't not support wasm debug
There has been no activity on this issue for 3 years and it may no longer be relevant. It will be closed 1 month after the last non-automated comment.
There has been no activity on this issue and it is being closed. If you feel closing this issue is not the right thing to do, please leave a comment.
What steps will reproduce the bug?
you can reproduce it in https://github.com/hardfist/wasm-demo,
How often does it reproduce? Is there a required condition?
What is the expected behavior?
What do you see instead?
Additional information