Hi, 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.
cheers, pl On 29 March 2016 at 00:21, Jeffrey Tan via lldb-dev <lldb-dev@lists.llvm.org> wrote: > Hi, > > 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 > siginal: > "Trace/breakpoint trap" > > I tried to call SBTarget.DeleteAllBreakpoints() first before killing > debugger. Still the same result. > > Jeffrey > > _______________________________________________ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > _______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev