On Tue, Nov 24, 2009 at 12:30:44AM -0200, Alexandre Oliva wrote:
> On Nov 23, 2009, Jack Howarth <howarth@xxxxxxxxxxxxxxxx> wrote:
> > It appears that we still must be missing some cases were
> > AT_location is being set to zero
> Can you name any? I'm using a cross compiler, so I need a testcase that
> triggers the problem, its assembly with -dA comments and an indication
> of where the problem is in it.
> Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
> You must be the change you wish to see in the world. -- Gandhi
> Be Free! -- http://FSFLA.org/ FSF Latin America board member
> Free Software Evangelist Red Hat Brazil Compiler Engineer
I am uncertain if the stock dwarfdump will provide the necessary
information to find any residual zero locations. I have uploaded
an archive of the remaining shared libs that cause dsymutil to
assert under radar://7415099 and have asked the darwin linker
maintainers to look at those. I'll let you know as soon as I hear
back if this is still the same issue with zero locations or something
different. Remember that they have been working from the limited
testcase in PR41473 and haven't tested full shared libs from FSF
gcc yet with their patched dsymutil. I specific it may still be
the zero locations problem though because dsymutil is stil asserting
on the same line...
Assertion failed: (orig_str), function FixReferences, file
/SourceCache/dwarf_utilities/dwarf_utilities-70/source/DWARFdSYM.cpp, line 3641.