kendalharland wrote: > Instead of assuming the thread's index or index ID, it might be a good idea > to have a little helper method that can look through the inferior's threads > to find the thread with the property that we care about. In this case, we're > looking for the thread that's stopped in a specific module (`a.out` in this > case). > > Concurrent execution and thread order is not guaranteed to be stable between > runs, even if in practice they end up being that way on some platforms. The > less we can rely on specific indices or IDs that "should" be correct, the > better.
Sounds reasonable. I'll work that out with a helper method and resend for review once I upload a new commit. @bulbazord any idea how I can access the module from the `SBThread` object? I'm having trouble finding the right API. https://github.com/llvm/llvm-project/pull/96685 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
