You're right. This seems to be a deeper problem with the (GDBRemote?)RegisterContext. Reading some combination of registers corrupts the cache. There just happened to be no invalidation between StopInfoThreadPlan::ShouldStop and the next ThreadPlanCallFunction (and there shouldn't need to be).
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
