DavidSpickett wrote: I plan to look at the PR in detail at some point, but for now...
> However, I haven't found a way to obtain the state of the thread plan stack > via the python api or the lldb command-line interface to use in a test. We > could potentially parse the logs in tests to get the thread plan stack, but > that seems too unreliable. > > Please share your thoughts, if you have any ideas on the matter. Could we check at a lower level? The reverse debugging tests wrap a real lldb-server in a Python class, you could do the same and check for single step and software break set packets during the time where lldb should not be using them. (or fake the entire debug server but I bet you'll have to provide all sorts of things to get it working) https://github.com/llvm/llvm-project/pull/151195 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
