<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:labath@google.com" title="labath@google.com">labath@google.com</a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - llvm-dwarfdump with DWARF3: error: Unable to resolve DW_LLE_offset_pair: base address unknown"
href="https://bugs.llvm.org/show_bug.cgi?id=44482">bug 44482</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>FIXED
</td>
</tr>
<tr>
<td style="text-align:right;">Fixed By Commit(s)</td>
<td>
</td>
<td>0541a9d4e7
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - llvm-dwarfdump with DWARF3: error: Unable to resolve DW_LLE_offset_pair: base address unknown"
href="https://bugs.llvm.org/show_bug.cgi?id=44482#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - llvm-dwarfdump with DWARF3: error: Unable to resolve DW_LLE_offset_pair: base address unknown"
href="https://bugs.llvm.org/show_bug.cgi?id=44482">bug 44482</a>
from <span class="vcard"><a class="email" href="mailto:labath@google.com" title="labath@google.com">labath@google.com</a>
</span></b>
<pre>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 <a href="show_bug.cgi?id=44482#c4">comment #4</a>)
<span class="quote">> 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)</span >
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..</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>