[lldb][tests] Automatically call compute_mydir (NFC)Eliminate boilerplate of having each test manually assign to `mydir` by calling`compute_mydir` in lldbtest.py.Differential Revision: https://r
[lldb][tests] Automatically call compute_mydir (NFC)Eliminate boilerplate of having each test manually assign to `mydir` by calling`compute_mydir` in lldbtest.py.Differential Revision: https://reviews.llvm.org/D128077
show more ...
[lldb] Check if thread was suspended during previous stop added.Encountered the following situation: Let we started thread T1 and it hitbreakpoint on B1 location. We suspended T1 and continued the
[lldb] Check if thread was suspended during previous stop added.Encountered the following situation: Let we started thread T1 and it hitbreakpoint on B1 location. We suspended T1 and continued the process.Then we started thread T2 which hit for example the same location B1.This time in a breakpoint callback we decided not to stop returningfalse.Expected result: process continues (as if T2 did not hit breakpoint) itsworkflow with T1 still suspended. Actual result: process do stops (as ifT2 callback returned true).Solution: We need invalidate StopInfo for threads that was previouslysuspended just because something that is already inactive can not be thereason of stop. Thread::GetPrivateStopInfo() may be appropriate place todo it, because it gets called (through Thread::GetStopInfo()) every timebefore process reports stop and user gets chance to changem_resume_state again i.e if we see m_resume_state == eStateSuspendedit definitely means it was set during previous stop and it also meansthis thread can not be stopped again (cos' it was frozen duringprevious stop).Differential revision: https://reviews.llvm.org/D80112