[llvm-bugs] [Bug 44482] llvm-dwarfdump with DWARF3: error: Unable to resolve DW_LLE_offset_pair: base address unknown

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=44482

labath at google.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED
 Fixed By Commit(s)|                            |0541a9d4e7

--- Comment #5 from labath at google.com ---
I've changed the error message in 0541a9d4e7, which I think should be a
sufficient fix for this issue. Please reopen the bug if you have any more
questions/concerns, etc.

(In reply to David Blaikie from comment #4)
> Yeah, sounds good to me. I /think/ we could go even further and say there's
> no base address on the CU? (that's the only way you could be missing a base
> address - or perhaps in this parsing logic the base address isn't provided
> if we use base_addressx & the address pool isn't available? hmm, yeah, looks
> like that's the case I think - so perhaps it needs to be pretty vague unless
> those extra states are tracked)

Yes, a bad base_addressx can cause the base address to become undefined. In
addition to that, I'd stop short of saying that a base address must be defined
in the CU, since one possible (though probably inefficient) implementation
strategy could be to skip DW_AT_low_pc, but instead have all location lists
start with a base address selection entry..

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20200109/4b2dfaab/attachment.html>