https://github.com/DavidSpickett commented:
Not actually a problem because this is the best we can do with the APIs we're given, but - > The description for a thread can change at any time. For example, a different > thread can change the description of a thread of interest while you try to > retrieve that description. Funny how many of these functions say the same sort of thing. So I just wanted to say that in general, if you want to move to more "safe" functions that are still in theory thread-unsafe, I'm ok with that. For instance if there is one API that returns a pointer to some mysterious kernel struct, and another that let's you provide a buffer you control the lifetime of - let's use the latter. Even if both are unsafe in other ways. For this PR, @Nerixyz can be the approver. https://github.com/llvm/llvm-project/pull/199983 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
