http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54572
--- Comment #14 from Ian Lance Taylor <ian at airs dot com> 2012-12-01 06:43:07
UTC ---
Thanks for the additional info.
#1 0x00007ffff7bb53be in build_address_map (addrs=0x7fffffffc710,
data=0x7fffffffcf1c,
error_callback=0x7ffff7ad51f0 <error_callback>, is_bigendian=0,
dwarf_str_size=360,
dwarf_str=0x7ffff7ff71e3 "integer(kind=4)", dwarf_ranges_size=0,
dwarf_ranges=0x7ffff7ff6000 <Address 0x7ffff7ff6000 out of bounds>,
dwarf_abbrev_size=253,
dwarf_abbrev=0x7ffff7ff708f
"\001\021\001%\016\023\vB\v\003\016\033\016\021\001\022\001\020\006",
dwarf_info_size=484, dwarf_info=0x7ffff7ff6eab <Address 0x7ffff7ff6eab out
of bounds>,
base_address=<optimized out>, state=<optimized out>) at
../../../trunk-git/libbacktrace/dwarf.c:1299
That is weird because it is showing the parameters in reverse order. Is that
what gdb normally does on your system? It doesn't seem to do it for other
functions.
Here gdb says that the value of dwarf_info is out of bounds. That is not good.
That is most likely the immediate cause of the problem. (dwarf_ranges is also
out of bounds, but that likely doesn't matter as dwarf_ranges_size is zero.)
It looks like it had trouble getting the debug info for the executable file
itself. Can you add the output of readelf -S on the executable?
