diff options
| author | Pavel Labath <labath@google.com> | 2017-05-25 10:50:06 +0000 |
|---|---|---|
| committer | Pavel Labath <labath@google.com> | 2017-05-25 10:50:06 +0000 |
| commit | 45dde2375627c6b8b9eaab553ca642a51583f0bf (patch) | |
| tree | 5ca8c57e35f969829ca4d22bbddc01a01a4322a9 /lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py | |
| parent | 0b5d6e5d0e093377e3b212093b999c3fec9c2b69 (diff) | |
| download | bcm5719-llvm-45dde2375627c6b8b9eaab553ca642a51583f0bf.tar.gz bcm5719-llvm-45dde2375627c6b8b9eaab553ca642a51583f0bf.zip | |
Recommit "RunThreadPlan: Fix halting logic in IgnoreBreakpoints = false"
This is a resubmit of r303732, which was reverted due to a regression.
The original patch caused a regression in TestLoadUnload, which has only showed
up when running the remote test suite. The problem there was that we interrupted
the target just as it has hit the rendezvous breakpoint in the dlopen call. This
meant that the stop reason was set to "breakpoint" even though the event would
not have been broadcast if we had not stopped the process. I fix this by
checking StopInfo->ShouldNotify() before stopping.
I also add a new test for the handling of conditional breakpoints in
expressions, which I noticed to be broken (pr33164)
Differential Revision: https://reviews.llvm.org/D33283
llvm-svn: 303848
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/call-function/TestCallUserDefinedFunction.py')
0 files changed, 0 insertions, 0 deletions
