boris.ulasevich added a comment. Yes, it is quite old story. Original issue was that breakpoint with false condition resumes execution in spite of completed step plan. There was two local fix proposals, but finally the issue was fixed by StopInfoBreakpoint::PerformAction and Thread::GetStopInfo reworking.
That change had side effect on Ubuntu platform, and now we have another side effect here: function call processing does not expect that in case of both (1) unprocessed breakpoint hit and (2) plan complete event GetStopInfo() can return breakpoint's StopInfo. For me the fix is correct: do not ask GetStopInfo, but simply check plan for complete. https://reviews.llvm.org/D29144 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
