Set correct ThreadStopInfo in case of trace event
authorAbhishek Aggarwal <abhishek.a.aggarwal@intel.com>
Mon, 1 Feb 2016 09:01:42 +0000 (09:01 +0000)
committerAbhishek Aggarwal <abhishek.a.aggarwal@intel.com>
Mon, 1 Feb 2016 09:01:42 +0000 (09:01 +0000)
commitc2c8ca1ce3de4d9d4013ab6da5d759f59515ec78
treecd8d3051386247f616e3e9b672e713a388b60bc2
parent1358d866593a6745dc510dcaf7c01c5cba9a7000
Set correct ThreadStopInfo in case of trace event

Summary:
 - The patch solves Bug 23478 and Bug 19311. Resolving
   Bug 23478 also resolves Bug 23039.
      Correct ThreadStopInfo is set for Linux and FreeBSD
      platforms.

 - Summary:
      When a trace event is reported, we need to check
      whether the trace event lands at a breakpoint site.

      If it lands at a breakpoint site then set the thread's
      StopInfo with the reason 'breakpoint'. Else, set the reason
      to be 'Trace'.

Change-Id: I0af9765e782fd74bc0cead41548486009f8abb87
Signed-off-by: Abhishek Aggarwal <abhishek.a.aggarwal@intel.com>
Reviewers: jingham, emaste, lldb-commits, clayborg, ovyalov

Subscribers: emaste

Differential Revision: http://reviews.llvm.org/D16720

llvm-svn: 259344
lldb/packages/Python/lldbsuite/test/functionalities/breakpoint/consecutive_breakpoints/TestConsecutiveBreakpoints.py
lldb/packages/Python/lldbsuite/test/functionalities/dynamic_value_child_count/TestDynamicValueChildCount.py
lldb/source/Plugins/Process/FreeBSD/FreeBSDThread.cpp
lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp