aboutsummaryrefslogtreecommitdiff
path: root/lldb/packages/Python/lldbsuite/test/configuration.py
diff options
context:
space:
mode:
authorDavid Stenberg <david.stenberg@ericsson.com>2020-03-18 11:32:03 +0100
committerDavid Stenberg <david.stenberg@ericsson.com>2020-03-18 13:23:17 +0100
commita0a3a9c5a83192254eae442654e65dd3eb724713 (patch)
tree299dcd0f96f9a9f30e9385c0afa8afda35891088 /lldb/packages/Python/lldbsuite/test/configuration.py
parent0db7244295b15181991a793e99fe9a1a0b54a56d (diff)
downloadllvm-a0a3a9c5a83192254eae442654e65dd3eb724713.zip
llvm-a0a3a9c5a83192254eae442654e65dd3eb724713.tar.gz
llvm-a0a3a9c5a83192254eae442654e65dd3eb724713.tar.bz2
[DebugInfo] Fix multi-byte entry values in call site values
Summary: In D67768/D67492 I added support for entry values having blocks larger than one byte, but I now noticed that the DIE implementation I added there was broken. The takeNodes() function, that moves the entry value block from a temporary buffer to the output buffer, would destroy the input iterator when transferring the first node, meaning that only that node was moved. In practice, this meant that when emitting a call site value using a DW_OP_entry_value operation with a DWARF register number larger than 31, that multi-byte DW_OP_regx expression would be truncated. Reviewers: djtodoro, aprantl, vsk Reviewed By: djtodoro Subscribers: llvm-commits Tags: #debug-info, #llvm Differential Revision: https://reviews.llvm.org/D76279
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/configuration.py')
0 files changed, 0 insertions, 0 deletions