Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

process interrupt not working unless a breakpoint has been hit #58

Closed
bartekb81 opened this issue Mar 8, 2018 · 3 comments
Closed

process interrupt not working unless a breakpoint has been hit #58

bartekb81 opened this issue Mar 8, 2018 · 3 comments
Labels
upstream-bug A bug that can be reproduced when purely using LLDB's Python API.

Comments

@bartekb81
Copy link

bartekb81 commented Mar 8, 2018

I get an LLDB error:

→ (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.

NVIM v0.2.2
lldb.nvim commit: dec080a

@johncf
Copy link
Member

johncf commented Mar 11, 2018

I suspect this is an upstream bug. To verify that, do this from your python2 REPL:

import lldb
dbg = 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 succeeded
res = 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!

@bartekb81
Copy link
Author

Yup. Thanks for help, I can confirm that...

@johncf johncf added the upstream-bug A bug that can be reproduced when purely using LLDB's Python API. label Mar 12, 2018
@johncf
Copy link
Member

johncf commented Mar 12, 2018

cc #59

@johncf 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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
upstream-bug A bug that can be reproduced when purely using LLDB's Python API.
Projects
None yet
Development

No branches or pull requests

2 participants