You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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 -1 and the program not working as expected
I can't reproduce on macos 10.14.6 with lldb 1001.0.13.3. The process exited with status -1 thing 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 -1 thing 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
Activity
bnoordhuis commentedon Jul 2, 2020
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?
devsnek commentedon Jul 2, 2020
More generally, I can't get
lldb -- nodeto not exit -1 on macOS (10.15.5)hardfist commentedon Jul 3, 2020
yeah, I mean
process exited with status -1and the program not working as expectedbnoordhuis commentedon Jul 3, 2020
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.What do you mean? Is "the program" node or lldb and what specifically isn't working as expected?
hardfist commentedon Jul 3, 2020
it should print "res: 5", but as you see in the screenshot, it just exit with exitcode -1 ,and print nothing
devsnek commentedon Jul 3, 2020
@hardfist can you try running
sudo DevToolsSecurity -enableand then testing this again?hardfist commentedon Jul 3, 2020
failed again

devsnek commentedon Jul 3, 2020
I can't repro anymore after enabling developer mode.
hardfist commentedon Jul 3, 2020
it works when using the latest node I build with source now , but the dwarf debug seems not working
bnoordhuis commentedon Jul 3, 2020
I've moved this to nodejs/help because it's likely a toolchain issue, almost certainly not an issue with node itself.
ggreif commentedon Jul 7, 2020
did you
?
hardfist commentedon Jul 8, 2020
yes, I set it on .lldbinit
ggreif commentedon Jul 8, 2020
I am asking because that made breakpoints of
lldb-10work for me, underwasmtime-0.17.hardfist commentedon Jul 8, 2020
yes , it works well for wasmtime but not nodejs
hardfist commentedon Jul 30, 2020
@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
github-actions commentedon Jul 31, 2023
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.
github-actions commentedon Aug 31, 2023
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.