jingham added a comment. My preference for things like crash reports would be that you make up a stop reason that's significant for the thread(s) you think are interesting and then let lldb figure out how to display them. After all, if you set a selected thread w/o having a StopInfo that would warrant selecting that thread, it's going to look weird. We selected thread 100, but it hadn't stopped for any particular reason is an odd experience.
And I don't think the default behavior should be to select thread 1, as that forces the upper layers hand. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D118482/new/ https://reviews.llvm.org/D118482 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
