[Lldb-commits] [PATCH] D29144: LLDB: fix for TestCallThatThrows.py test fail

Boris Ulasevich via Phabricator via lldb-commits lldb-commits at lists.llvm.org
Fri Jan 27 11:54:53 PST 2017

boris.ulasevich added a comment.

In https://reviews.llvm.org/D29144#657798, @jingham wrote:

> When you go to pick the plan to report for the stop it should be the top of the completed plan stack, the "thread plan to call function".  Why in this particular case is the bottom of the completed stack getting handed out?

"thread plan to call function" do stay on the top of the completed plan stack, but GetStopInfo returns another value because ProcessGDBRemote::SetThreadStopInfo have put StopInfoBreakpoint to Thread::m_stop_info_sp, and preset value have priority over completed plan.



More information about the lldb-commits mailing list