Re: [lldb-dev] SBProcess::Detach kills target

Just a wild guess - is this SIGHUP because stdin/stdout are broken? I.e. the debugger closes its pty's on detach and that causes the signal?What is the behavior on MAC? To: lab...@google.com Date: Wed, 30 Mar 2016 14:49:33 -0700 CC: lldb-dev@lists.llvm.org Subject: Re: [lldb-dev]

Re: [lldb-dev] SBProcess::Detach kills target

Right, my bad. The problem was that when debugger detaches the stdio does not go anywhere so I failed to see my printf. Still, is this how it is supposed to be? I naively assume that if we don't send SIGHUP in attach scenario we should not send it in launch scenario too. Thanks,Eugene > From:

Re: [lldb-dev] SBProcess::Detach kills target

So I have made a small test program (which does nothing but spin in a loop), and indeed it is the SIGHUP that kills it after detach. If the test program blocks the signal, then it continues running even after detach: $ cat a.c #include #include int main() { signal(SIGHUP, SIG_IGN); for

Re: [lldb-dev] Inquiry about LLDB remote protocol

Thank you all for the information. On Tue, Mar 29, 2016 at 7:25 PM, Greg Clayton wrote: > > > On Mar 29, 2016, at 2:57 AM, Ravitheja Addepally via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > > > Hello, > > I wanted to know if the remote protocol of LLDB is state