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
→ (lldb) target create ...
✓ Current executable set to '...' (x86_64).
→(lldb) process launch
✓ Process 90358 launched: ...' (x86_64)
→ (lldb) process interrupt
✗error: Failed to halt process: Process is not running.
This does not happen if I set a breakpoint somewhere, make the process hit it and then try again.
I suspect this is an upstream bug. To verify that, do this from your python2 REPL:
importlldbdbg=lldb.SBDebugger.Create()
ci=dbg.GetCommandInterpreter()
res=lldb.SBCommandReturnObject()
ci.HandleCommand("target create ...", res)
# use the following whenever you want:#print(res.Succeeded())#print(res.GetOutput())#print(res.GetError()) # if not succeededres=lldb.SBCommandReturnObject()
ci.HandleCommand("process launch", res)
res=lldb.SBCommandReturnObject()
ci.HandleCommand("process interrupt", res)
The plugin is basically a wrapper around that. Nothing too fancy!
johncf
changed the title
:LL Process interrupt not working until at least one breakpoint has been hit
process interrupt not working unless a breakpoint has been hit
Mar 12, 2018
I get an LLDB error:
This does not happen if I set a breakpoint somewhere, make the process hit it and then try again.
NVIM v0.2.2
lldb.nvim commit: dec080a
The text was updated successfully, but these errors were encountered: