The "step" log should show you if any code got run between the stop to evaluate "ShouldStop" and when you go to get the register context here. I would be surprised if this is happening, however. If any thread plans need to run code to do some task, they just push another ThreadPlanCallFunction, return false from ShouldStop and then the secondary call get done in the course of handling the thread plans.
I suspect the thread plugin is not properly managing its register context. The ThreadPlan code just calls m_thread.GetRegisterContext(), we're stopped so that should always return a valid register context. Maybe when we ran the old context was not invalidated as it should have been? http://reviews.llvm.org/D8643 EMAIL PREFERENCES http://reviews.llvm.org/settings/panel/emailpreferences/ _______________________________________________ lldb-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits
