Hi,

This is a follow-up to the "Problems with startup code symbols (Copious
warnings)" gdb@ thread found here:
http://sources.redhat.com/ml/gdb/2006-06/msg00051.html

The attached patch replaces the HAS_RELOC checks in dwarf2read.c with a
per-objfile lookup for a section loaded at 0. With this modification,
non-relocatable files that have a code at address 0 should be handled
better (no discarded debug information). 
As Daniel pointed out in the referenced thread, this solution isn't
perfect because you can have valid code at 0 and at the same time
'orphaned' debug info that seemingly references the 0 address. However
in the long run tools should correctly handle things like .gnu.linkonce,
and with correct debug info this patch looks like the right thing. (BTW,
was my testing defficient, or do recent GNU toolchains handle linkonce
sections and associated debug info correctly?)

I regression tested this on native i686-pc-linux-gnu.

Steven, by re-reading the thread that initiated this proposal I'm not
sure that this will really change something for you because the subject
had a bit diverged from your particular problem. Nevertheless could you
still give it a try to see if it helps with your warning issue?

:ADDPATCH Dwarf2:

(Nice side-effect of the patch tracker: It reminded me that I needed to
actually attach the patch :-) )

Cheers,
Fred