[PATCH] D136395: Add the ability to verify the .debug_aranges section.

[Greg Clayton via Phabricator via llvm-commits]

clayborg added a comment.

In D136395#3880237 <https://reviews.llvm.org/D136395#3880237>, @probinson wrote:

> We (Sony) also have some tooling that relies on .debug_aranges; while I sympathize with wanting to get rid of it, and I've filed a ticket to update the relevant tooling, we're not there yet.
> Actually getting rid of .debug_aranges would probably deserve an RFC to raise the visibility, because there are clearly tools in various odd places that expect it to be there.  But if that process is not imminent, I'm not opposed to introducing verification to make sure we get it right.

I agree here. We have some internal tools that rely on this section.

LLDB currently will use it if it is available, then it falls back to the DW_AT_ranges or DW_AT_low_pc/DW_AT_high_pc of the compile unit if any of the attributes are present, and falls back to looking for ranges manually if neither are there.

After seeing issues with the .debug_aranges with modern clang builds, I am tempted to stop using .debug_aranges at all in LLDB and might make a patch for this.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D136395/new/

https://reviews.llvm.org/D136395