summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/commands/command/script/bug11569.py
diff options
context:
space:
mode:
authorJeremy Morse <jeremy.morse.llvm@gmail.com>2019-09-02 12:28:36 +0000
committerJeremy Morse <jeremy.morse.llvm@gmail.com>2019-09-02 12:28:36 +0000
commit22493f66f168cf3cf8512e42b4ffb32f3f30b949 (patch)
treed1bbcfeebaf3ab31989303cfba7f3cbf2c4d764f /lldb/packages/Python/lldbsuite/test/commands/command/script/bug11569.py
parent9bc338b89ec02cdb87d54ef9d431544c52b7774a (diff)
downloadbcm5719-llvm-22493f66f168cf3cf8512e42b4ffb32f3f30b949.tar.gz
bcm5719-llvm-22493f66f168cf3cf8512e42b4ffb32f3f30b949.zip
[DebugInfo] LiveDebugValues: correctly discriminate kinds of variable locations
The missing line added by this patch ensures that only spilt variable locations are candidates for being restored from the stack. Otherwise, register or constant-value information can be interpreted as a spill location, through a union. The added regression test replicates a scenario where this occurs: the stack load from [rsp] causes the register-location DBG_VALUE to be "restored" to rsi, when it should be left alone. See PR43058 for details. Un x-fail a test that was suffering from this from a previous patch. Differential Revision: https://reviews.llvm.org/D66895 llvm-svn: 370648
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/commands/command/script/bug11569.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud