non-contiguous files break dwarf2 init-file recognition

[Alexandre Oliva]

If an object file contains functions in CODE sections that are mapped
to different segments, or just non-contiguous memory areas, and the
entry point of the program happens to be in between such areas, we may
end up picking the wrong comp_unit as init file.  This patch fixes it
(as long as the code of the init file itself is contiguous, this
should be fine, otherwise the whole thing has to be redesigned).  Ok
to install?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: gdb-non-contig-comp-unit.patch
Type: text/x-patch
Size: 1901 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20021211/f8f61ed3/attachment.bin>
-------------- next part --------------

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer