[Bug c++/15831] bad debug info

wilson at specifixinc dot com gcc-bugzilla@gcc.gnu.org
Mon Aug 16 19:27:00 GMT 2004


------- Additional Comments From wilson at specifixinc dot com  2004-08-16 19:27 -------
Subject: Re:  bad debug info

igodard at pacbell dot net wrote:
> ------- Additional Comments From igodard at pacbell dot net  2004-08-15 07:42 -------
> I don't have a more recent gdb available, and while I am prodding our sysadmin, that is not likely to get much soon. I uploaded the binary - what happens if you try a more recent gdb?

I took a quick look.  readelf -w can be used to look at the debug info.
  The functions debug info looks OK.  The function has been inlined, and
there is out out-of-line instance of it.

readelf does report an error
readelf: Error: Not enough comp units for .debug_lines section
but this seems to be harmless.  I would guess that this is a
gcc/binutils problem with unused sections being optimized away in the
linker.  So we just are optimizing away all of the unused debug info.

I tried gdb 6.1, and it seemed to work fine.  I could step through the
function after setting a breakpoint there.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15831



More information about the Gcc-bugs mailing list