Changes from Git (git http://labmaster3.local/git/llvm-project.git)


  1. [lldb] Move register info "augmentation" from gdb-remote into ABI (details)
  2. [lldb] Remove tab from (details)
  3. [DWARF] Add support for parsing/dumping section indices in location (details)
  4. Fixup 6d18e53: xfail properly (details)
Commit 2b8db387f2a616f39a077ede18c6366f2ea9f203 by pavel
[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:
The file was modifiedlldb/include/lldb/Target/ABI.h
The file was addedlldb/packages/Python/lldbsuite/test/functionalities/gdb_remote_client/basic_eh_frame.yaml
The file was modifiedlldb/packages/Python/lldbsuite/test/functionalities/gdb_remote_client/
The file was modifiedlldb/source/Target/ABI.cpp
The file was modifiedlldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
Commit 46d0ec3a803021281c8d868b1487d2d5cd06f274 by Raphael Isemann
[lldb] Remove tab from
Mixing tabs and spaces makes Python exit with this error:
line 23
   return (self.getArchitecture() == "aarch64" and self.getPlatform() ==
       ^ TabError: inconsistent use of tabs and spaces in indentation
The file was modifiedlldb/packages/Python/lldbsuite/test/functionalities/return-value/
Commit 1fbe8a82e1ea0168ee10079a18140135222d1d2c by pavel
[DWARF] Add support for parsing/dumping section indices in location
Summary: This does exactly what it says on the box. The only small
gotcha is the section index computation for offset_pair entries, which
can use either the base address section, or the section from the
offset_pair entry. This is to support both the cases where the base
address is relocated
(points to the base of the CU, typically), and the case where the base
address is a constant (typically zero) and relocations are on the
offsets themselves.
Reviewers: dblaikie, JDevlieghere, aprantl, SouraVX
Subscribers: hiraditya, llvm-commits, probinson
Tags: #llvm
Differential Revision:
The file was modifiedllvm/lib/DebugInfo/DWARF/DWARFDebugLoc.cpp
The file was modifiedllvm/test/tools/llvm-dwarfdump/X86/debug_loclists.s
The file was modifiedllvm/lib/DebugInfo/DWARF/DWARFDie.cpp
The file was modifiedllvm/lib/DebugInfo/DWARF/DWARFContext.cpp
The file was modifiedllvm/include/llvm/DebugInfo/DWARF/DWARFDebugLoc.h
The file was modifiedllvm/test/DebugInfo/X86/dwarfdump-debug-loc-simple.test
Commit 057626b4393836e11712bd694afda121d8309973 by diana.picus
Fixup 6d18e53: xfail properly
Forgot to squash this...
The file was modifiedlldb/packages/Python/lldbsuite/test/functionalities/show_location/