[llvm] [llvm][dwarf][rfc][donotcommit] Enable print of ranges addresses from .debug_info.dwo (PR #65516)

[David Blaikie via llvm-commits]

dwblaikie wrote:

> This is 100% split dwarf specific. Main usage model is to be able to dump out .debug_info.dwo either full or specific dies (with usual optional parent/children flags), and see addresses and ranges. So to bring the functionality of monolithic dwarf to split-dwarf space.

I'm trying to ask about the higher level goal - what's the problem you were trying to address by dumping this information? Presumably you were looking to see if some piece of the DWARF encoded some data correctly, etc? And what I'm asking is, if the binary hadn't been built with Split DWARF, what would be the right tools to help dump just the data you're interested in? (eg: if you were looking at a specific function and wanted to see how the address ranges of the function were emitted - the ability to search the DWARF by function name, using the index, or scoping it to a specific file could be useful - and that could be suitable with or without Split DWARF)

And if we had /that/ tool, and made it work with Split DWARF too, then we'd have a more unified mechanism for answering that sort of question.

https://github.com/llvm/llvm-project/pull/65516