[lldb-dev] How to detach from stop mode without causing signal in inferior on Linux?
Pavel Labath via lldb-dev
lldb-dev at lists.llvm.org
Tue Mar 29 02:08:56 PDT 2016
are you doing a SBProcess.Detach() before you kill the debugger? If
that doesn't help could you send me the gdb-remote packet form
(execute command: log enable -f /some/file.log gdb-remote packets), so
I can get a better idea of what is going on.
On 29 March 2016 at 00:21, Jeffrey Tan via lldb-dev
<lldb-dev at lists.llvm.org> wrote:
> When user tries to stop debugging, we call SBDebugger.Destroy(), then
> SBDebugger.Terminate() and exit the python process. This works well on mac,
> but on linux in running mode. However, I found if the debugger hits
> breakpoint first, then user stops debugging, the inferior is killed with
> "Trace/breakpoint trap"
> I tried to call SBTarget.DeleteAllBreakpoints() first before killing
> debugger. Still the same result.
> lldb-dev mailing list
> lldb-dev at lists.llvm.org
More information about the lldb-dev