summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lang/cpp/breakpoint-commands/nested.cpp
diff options
context:
space:
mode:
authorLuke Cheeseman <luke.cheeseman@arm.com>2018-12-21 10:45:08 +0000
committerLuke Cheeseman <luke.cheeseman@arm.com>2018-12-21 10:45:08 +0000
commit41a9e53500c4317da7fa0d0b52322ea5df78a796 (patch)
treed4c709f59ed2515613b75049277278bc6f3d9b99 /lldb/packages/Python/lldbsuite/test/lang/cpp/breakpoint-commands/nested.cpp
parent82fbb664657da2f635dc03e1e656649dbdb6c3c0 (diff)
downloadbcm5719-llvm-41a9e53500c4317da7fa0d0b52322ea5df78a796.tar.gz
bcm5719-llvm-41a9e53500c4317da7fa0d0b52322ea5df78a796.zip
[Dwarf/AArch64] Return address signing B key dwarf support
- When signing return addresses with -msign-return-address=<scope>{+<key>}, either the A key instructions or the B key instructions can be used. To correctly authenticate the return address, the unwinder/debugger must know which key was used to sign the return address. - When and exception is thrown or a break point reached, it may be necessary to unwind the stack. To accomplish this, the unwinder/debugger must be able to first authenticate an the return address if it has been signed. - To enable this, the augmentation string of CIEs has been extended to allow inclusion of a 'B' character. Functions that are signed using the B key variant of the instructions should have and FDE whose associated CIE has a 'B' in the augmentation string. - One must also be able to preserve these semantics when first stepping from a high level language into assembly and then, as a second step, into an object file. To achieve this, I have introduced a new assembly directive '.cfi_b_key_frame ', that tells the assembler the current frame uses return address signing with the B key. - This ensures that the FDE is associated with a CIE that has 'B' in the augmentation string. Differential Revision: https://reviews.llvm.org/D51798 llvm-svn: 349895
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/cpp/breakpoint-commands/nested.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud