Now -exec-next command uses SB API for stepping over.
|384 ↗||(On Diff #150035)|
It looks like this branch is not covered by the test. Also, do we care about what happens when the client specifies an invalid thread id?
|19 ↗||(On Diff #150137)|
I was surprised by that as well, so I tried a some experiments. I don't know how or why, but lldb-mi seems to use it's own notion of thread-ids, which are independent of os-level ids and always start with one. I guess they are just indexes into the list of threads. I don't know if that is intentional or what.
|384 ↗||(On Diff #150137)|
Yes, that's the issue I was alluding to. I am not going to block this patch over it or anything, but I want to make sure you are aware that you're hitting the limitations of the FileCheck test approach already.
That said, if what I said above about the thread-id's always being numbered starting from one is true, then the thread ids may be predictable enough to test using -exec-next --thread 1 and avoid this problem for now.