Stop-hooks weren't getting called on step-out. Fix that.
authorJim Ingham <jingham@apple.com>
Thu, 15 Aug 2019 21:37:52 +0000 (21:37 +0000)
committerJim Ingham <jingham@apple.com>
Thu, 15 Aug 2019 21:37:52 +0000 (21:37 +0000)
commit7049b0ad4d610497939c9b2eaa72deb5f6dc989e
tree54c79e23887a0effb61178aeb82f64aa8508be3b
parentfdee340beabd13f9bb5a3203ab4cbeaec48d4d9b
Stop-hooks weren't getting called on step-out. Fix that.

There was a little bit of logic in the StopInfoBreakpoint::PerformAction
that would null out the StopInfo once we had a completed plan so that the
next call to GetStopInfo would replace it with the StopInfoThreadPlan.

But the stop-hooks check for whether a thread stopped for a reason didn't
trigger this conversion.  So I added an API to do that directly, and then
called it where before we just reset the StopInfo.

<rdar://problem/54270767>

Differential Revision: https://reviews.llvm.org/D66241

llvm-svn: 369052
lldb/include/lldb/Target/Thread.h
lldb/packages/Python/lldbsuite/test/functionalities/stop-hooks/Makefile [new file with mode: 0644]
lldb/packages/Python/lldbsuite/test/functionalities/stop-hooks/TestStopHooks.py [new file with mode: 0644]
lldb/packages/Python/lldbsuite/test/functionalities/stop-hooks/main.c [new file with mode: 0644]
lldb/source/Target/StopInfo.cpp
lldb/source/Target/Thread.cpp