Re: _bfd_dwarf2_find_nearest_line returns wrong filename

[Andreas Schwab <schwab at suse dot de>]

Daniel Jacobowitz <drow@mvista.com> writes:

|> On Fri, Jan 03, 2003 at 03:39:40PM +0100, Andreas Schwab wrote:
|> > Daniel Jacobowitz <drow@mvista.com> writes:
|> > 
|> > |> No regressions, but some pertinent facts:
|> > |> 
|> > |>  - Examine the ld.log with this patch applied.  Grep for BFD.  You'll
|> > |>    find several assertion failures indicating that the DWARF-2 data
|> > |>    is incorrect.  It's kind of sad that the testsuite doesn't notice any
|> > |>    of these.
|> > 
|> > I have now tried it on ia64, and it is getting worse.  They are using
|> > R_IA64_SECREL32LS relocations in .debug_info, which is causing
|> > bfd_perform_relocation to return bfd_reloc_outofrange, and
|> > bfd_generic_get_relocated_section_contents is aborting on that.
|> 
|> We needed to save and restore outputs in order to get the right answers
|> on i386 in some cases.  We also needed some other fixes to ia64 - I
|> missed it when I swept the hash table create functions to make them use
|> bfd_malloc, I guess - and to weaken an abort in elfNN_ia64_reloc.  But
|> now it works.

This does not seem to work in the linker, it doesn't emit any filename
prefixes any more.  This also causes testsuite failures, the ld-elfvsb
tests depend on the filename part of the error messages.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."