You might be able to set LLDB_DEBUGSERVER_LOG_FILE in the lldb program's environment with a path, then set LLDB_SERVER_LOG_CHANNELS to a set of channels that lldb-server will use when logging. It might give you some insight as to what is going on. These environment variables will get passed along to the lldb-server when it runs allowing lldb-server to log anything so you might be able to tell what is going on.
> On Apr 4, 2019, at 9:44 AM, Steve Ravet via lldb-dev > <lldb-dev@lists.llvm.org> wrote: > > lldb developers, I am having a problem with lldb that I hope you can help > with. I am debugging some C++ by running it, and attaching to the process > with lldb. I get a nonsensical backtrace like this: > > thread #37, name = 'xmsim', stop reason = signal SIGSTOP > frame #0: 0x00002b96a2ab1409 > thread #38, name = 'xmsim', stop reason = signal SIGSTOP > frame #0: 0x00002b96a2ab1409 > thread #39, name = 'xmsim', stop reason = signal SIGSTOP > frame #0: 0x00002b96a2ab1409 > thread #40, name = 'xmsim', stop reason = signal SIGSTOP > frame #0: 0x00002b96a2ab1409 > thread #41, name = 'xmsim', stop reason = signal SIGSTOP > frame #0: 0x00002b96a2ab1409 > thread #42, name = 'xmsim', stop reason = signal SIGSTOP > frame #0: 0x00002b96a2ab1409 > > And the first lldb command I try, I get the message in the subject, and the > debug session is dead. > > I am on CentOS 6 with no possibility of moving to something newer. I had > this problem with lldb 6.0.0, but recently moved to lldb 8.0.0 and still have > it. The compile toolchain is llvm 6.0.0. Where do I look to further debug > this, either why the process exited or why the debugserver died? > > thanks, > --steve > _______________________________________________ > lldb-dev mailing list > lldb-dev@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
