<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div>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.</div><div><br class=""></div><div><div style="margin: 0px; font-stretch: normal; line-height: normal; color: rgb(196, 26, 22); background-color: rgb(255, 255, 255);" class=""><br class=""></div></div><div><blockquote type="cite" class=""><div class="">On Apr 4, 2019, at 9:44 AM, Steve Ravet via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org" class="">lldb-dev@lists.llvm.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">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:<br class=""><br class=""> thread #37, name = 'xmsim', stop reason = signal SIGSTOP<br class=""> frame #0: 0x00002b96a2ab1409<br class=""> thread #38, name = 'xmsim', stop reason = signal SIGSTOP<br class=""> frame #0: 0x00002b96a2ab1409<br class=""> thread #39, name = 'xmsim', stop reason = signal SIGSTOP<br class=""> frame #0: 0x00002b96a2ab1409<br class=""> thread #40, name = 'xmsim', stop reason = signal SIGSTOP<br class=""> frame #0: 0x00002b96a2ab1409<br class=""> thread #41, name = 'xmsim', stop reason = signal SIGSTOP<br class=""> frame #0: 0x00002b96a2ab1409<br class=""> thread #42, name = 'xmsim', stop reason = signal SIGSTOP<br class=""> frame #0: 0x00002b96a2ab1409<br class=""><br class="">And the first lldb command I try, I get the message in the subject, and the debug session is dead.<br class=""><br class="">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?<br class=""><br class="">thanks,<br class="">--steve<br class="">_______________________________________________<br class="">lldb-dev mailing list<br class=""><a href="mailto:lldb-dev@lists.llvm.org" class="">lldb-dev@lists.llvm.org</a><br class="">https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev<br class=""></div></div></blockquote></div><br class=""></body></html>