labath added a comment. Since the failure reason was not very obvious from the bot message, I took a quick look, and to save you the trouble of reproducing this, here's what I found:
The reason the new test failed was because the symbols you are searching for (`__GI_raise`, `__GI___assert_fail`) are private libc symbols which are only available if you happen to have debug info for the system libc installed. If you don't, these will show up as `raise` and `__assert_fail`, respectively. Also the TestExitDuringStep was failing because of some apparent memory corruption in the stop reason (I am getting output like `* thread #2, name = 'a.out', stop reason = P�4��` Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D73303/new/ https://reviews.llvm.org/D73303 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
