How to determine cause of ld testsuite failures?

[H . J . Lu]

On Fri, Feb 16, 2001 at 01:08:14AM -0800, David O'Brien wrote:
> On Fri, Feb 16, 2001 at 06:25:24PM +1100, Alan Modra wrote:
> > > > > How would people suggest I go about fixing the failures?
> > > > First, have a look at ld/ld.log to see some details of the failures.
> 
> The last failure needs a tweak to the test script to expect the failure.
> The comment in ld/testsuite/ld-undefined/undefined.exp explains what is
> going on.
> 
> Ok to commit to both mainline and the 2_11 branch?
> 
> 
> --- undefined.exp.orig	Fri Feb 16 00:55:04 2001
> +++ undefined.exp	Fri Feb 16 00:57:15 2001
> @@ -124,11 +124,12 @@
>  #   undefined.0(.text+0xc): undefined reference to `this_function_is_not_defined'
>  #
>  # hence the xfails below.
>  
>  #setup_xfail arm-*-elf
>  #setup_xfail strongarm-*-elf
>  #setup_xfail thumb-*-elf
>  setup_xfail mcore-*-elf
>  setup_xfail mips-sgi-irix6*
> +setup_xfail i*86-*-freebsd4*
>  
>  checkund $ml $testline

I don't understand why people don't fix BFD, but just mark it as
expected to fail. FYI, Nick has checked in my patch to fix BFD
in the main trunk:

2001-02-14  H.J. Lu  <hjl@gnu.org>

        * elf.c (elf_find_function): New function.
        (_bfd_elf_find_nearest_line): Call elf_find_function () to find
        the file name and function name.

BTW, I noticed it on Linux/ia64 which uses dwarf-2. 

-- 
H.J. Lu (hjl@valinux.com)