labath added a comment. Well... I'm as puzzled as you are. Whatever the problem is, it seems to be limited to debian (kernel). I've filed a bug about that: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014754.
One good thing I learned is that this problem seems to be limited to SIGSTOPs, so it should be possible to work around it by using some other signal. That's probably a good idea anyway, since SIGSTOP has the unpleasant property of leaving around a stopped zombie if something goes wrong (that's what killed the bot over the weekend). Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D129012/new/ https://reviews.llvm.org/D129012 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
