[all-commits] [llvm/llvm-project] 434905: Run all threads when extending a next range over a...
jimingham via All-commits
all-commits at lists.llvm.org
Mon Dec 16 17:48:20 PST 2019
Branch: refs/heads/master
Home: https://github.com/llvm/llvm-project
Commit: 434905b97d961531286d4b49c7ee1969f7cbea0e
https://github.com/llvm/llvm-project/commit/434905b97d961531286d4b49c7ee1969f7cbea0e
Author: Jim Ingham <jingham at apple.com>
Date: 2019-12-16 (Mon, 16 Dec 2019)
Changed paths:
M lldb/include/lldb/Core/Disassembler.h
M lldb/include/lldb/Target/ThreadPlanStepRange.h
M lldb/packages/Python/lldbsuite/test/commands/expression/no-deadlock/Makefile
M lldb/packages/Python/lldbsuite/test/commands/expression/no-deadlock/TestExprDoesntBlock.py
R lldb/packages/Python/lldbsuite/test/commands/expression/no-deadlock/locking.c
A lldb/packages/Python/lldbsuite/test/commands/expression/no-deadlock/locking.cpp
A lldb/packages/Python/lldbsuite/test/lang/c/step_over_no_deadlock/Makefile
A lldb/packages/Python/lldbsuite/test/lang/c/step_over_no_deadlock/TestStepOverDoesntBlock.py
A lldb/packages/Python/lldbsuite/test/lang/c/step_over_no_deadlock/locking.cpp
M lldb/source/Core/Disassembler.cpp
M lldb/source/Target/Process.cpp
M lldb/source/Target/ThreadPlanStepRange.cpp
Log Message:
-----------
Run all threads when extending a next range over a call.
If you don't do this you end up running arbitrary code with
only one thread allowed to run, which can cause deadlocks.
<rdar://problem/56422478>
Differential Revision: https://reviews.llvm.org/D71440
More information about the All-commits
mailing list