llvm-project/lldb/unittests/Thread/CMakeLists.txt

add_lldb_unittest(ThreadTests
  ThreadTest.cpp

  LINK_LIBS
      lldbCore
      lldbHost
      lldbTarget
      lldbSymbol
      lldbUtility
      lldbUtilityHelpers
      lldbInterpreter
      lldbBreakpoint
      lldbPluginPlatformLinux
  )
[lldb/Test] Fix unittest name Lit looks for the Tests prefix in the unit test name. 2020-06-13 05:00:57 +08:00			`add_lldb_unittest(ThreadTests`
[lldb] Check if thread was suspended during previous stop added. Encountered the following situation: Let we started thread T1 and it hit breakpoint 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 returning false. Expected result: process continues (as if T2 did not hit breakpoint) its workflow with T1 still suspended. Actual result: process do stops (as if T2 callback returned true). Solution: We need invalidate StopInfo for threads that was previously suspended just because something that is already inactive can not be the reason of stop. Thread::GetPrivateStopInfo() may be appropriate place to do it, because it gets called (through Thread::GetStopInfo()) every time before process reports stop and user gets chance to change m_resume_state again i.e if we see m_resume_state == eStateSuspended it definitely means it was set during previous stop and it also means this thread can not be stopped again (cos' it was frozen during previous stop). Differential revision: https://reviews.llvm.org/D80112 2020-06-12 05:59:19 +08:00			`ThreadTest.cpp`

			`LINK_LIBS`
			`lldbCore`
			`lldbHost`
			`lldbTarget`
			`lldbSymbol`
			`lldbUtility`
			`lldbUtilityHelpers`
			`lldbInterpreter`
			`lldbBreakpoint`
			`lldbPluginPlatformLinux`
			`)`