summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPythonImpl.h
diff options
context:
space:
mode:
authorPavel Labath <pavel@labath.sk>2019-12-03 11:39:20 +0100
committerPavel Labath <pavel@labath.sk>2019-12-03 11:39:20 +0100
commit2b8db387f2a616f39a077ede18c6366f2ea9f203 (patch)
treebc031616f89a752df513eeb04662dbf0ab64d992 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPythonImpl.h
parent09667bc1920463107684a566c3f2c3cef9b156e7 (diff)
downloadbcm5719-llvm-2b8db387f2a616f39a077ede18c6366f2ea9f203.tar.gz
bcm5719-llvm-2b8db387f2a616f39a077ede18c6366f2ea9f203.zip
[lldb] Move register info "augmentation" from gdb-remote into ABI
Summary: Previously the ABI plugin exposed some "register infos" and the gdb-remote code used those to fill in the missing bits. Now, the "filling in" code is in the ABI plugin itself, and the gdb-remote code just invokes that. The motivation for this is two-fold: a) the "augmentation" logic is useful outside of process gdb-remote. For instance, it would allow us to avoid repeating the register number definitions in minidump code. b) It gives more implementation freedom to the ABI classes. Now that these "register infos" are essentially implementation details, classes can use other methods to obtain dwarf/eh_frame register numbers -- for instance they can consult llvm MC layer. Since the augmentation code was not currently tested anywhere, I took the opportunity to create a simple test for it. Reviewers: jasonmolenda, clayborg, tatyana-krasnukha Subscribers: aprantl, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D70906
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPythonImpl.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud