Re: non-contiguous files break dwarf2 init-file recognition

[Alexandre Oliva <aoliva at redhat dot com>]

On Dec 11, 2002, Elena Zannoni <ezannoni@redhat.com> wrote:

> http://sources.redhat.com/ml/gdb-patches/2001-12/msg00616.html
> Would that patch help you here?
> Probably not.

Definitely not.  The case at hand has debugging info for a function
whose oddly-named section was explicitly discarded by a linker script,
but whose lowpc was not at the beginning of the section, so, even
though the section address ended up as zero, it wasn't zero for lowpc
of the function, so the lowpc==0 test in dwarf2_get_pc_bounds() didn't
pass and the debugging info for the function was not discarded.

Then, since the comp_unit had code in .text too, the final
lowpc/highpc region contained all code from zero to the end of the
.text code in the comp_unit, and the program entry point happened to
be in between, so we thought that comp_unit was the entry_file, and
the excessively-inclusive region ended up being used to tell whether
a stack trace had got to the top of the stack.

-- 
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