diff options
| author | Jeremy Morse <jeremy.morse.llvm@gmail.com> | 2019-10-04 09:38:05 +0000 |
|---|---|---|
| committer | Jeremy Morse <jeremy.morse.llvm@gmail.com> | 2019-10-04 09:38:05 +0000 |
| commit | 0ca48de26c46281ae9fd15a042cc19cdf316bee6 (patch) | |
| tree | cb064e755f388456e0f3d29e66b9ef7e1fde6e64 /lldb/packages/Python/lldbsuite/test/python_api/debugger/TestDebuggerAPI.py | |
| parent | 4128dc4500693beb29e4f7cdf3f548c27bebbb9a (diff) | |
| download | bcm5719-llvm-0ca48de26c46281ae9fd15a042cc19cdf316bee6.tar.gz bcm5719-llvm-0ca48de26c46281ae9fd15a042cc19cdf316bee6.zip | |
[DebugInfo] LiveDebugValues: defer DBG_VALUE creation during analysis
When transfering variable locations from one place to another,
LiveDebugValues immediately creates a DBG_VALUE representing that
transfer. This causes trouble if the variable location should
subsequently be invalidated by a loop back-edge, such as in the added
test case: the transfer DBG_VALUE from a now-invalid location is used
as proof that the variable location is correct. This is effectively a
self-fulfilling prophesy.
To avoid this, defer the insertion of transfer DBG_VALUEs until after
analysis has completed. Some of those transfers are still sketchy, but
we don't propagate them into other blocks now.
Differential Revision: https://reviews.llvm.org/D67393
llvm-svn: 373720
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/debugger/TestDebuggerAPI.py')
0 files changed, 0 insertions, 0 deletions
