[PATCH] D36097: Prototype fix for lld DWARF parsing of base address selection entries in range lists
George Rimar via llvm-commits
llvm-commits at lists.llvm.org
Wed Aug 2 09:29:52 PDT 2017
>>?I do not think we have. That looks to be my fault, I don't think I added
>>LLVM testcase when implemented section index API.
>>I'll check what can I do for it.
>
>I'm guessing it'll need to be a unit test - I don't imagine the section index is used by any of the LLVM tools (llvm-dwarfdump or >llvm-symbolizer). /maybe/ there's a useful thing that could be exposed using SectionIndex in dwarfdump (eg: llvm-dwarfdump >on an object could print the name of a section next to any addresses - which could be handy when reading ranges and the like)
I plan to work on this tomorrow. I think it probably can be testcase for .gdb_index dumping in dwardump,
we could dump not only low/high addresses of address area but also a section index/name this range belongs to.
That probably can be helpfull to reveal issues like this patch tries to fix.
I'll try to check and find how much it can be useful, still going to test your example first
($ clang-tot test.cpp -g -c -mllvm -use-dwarf-ranges-base-address-specifier).
George.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20170802/66374f80/attachment-0001.html>
More information about the llvm-commits
mailing list