This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info
- From: "dberlin at dberlin dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 30 Dec 2004 05:10:33 -0000
- Subject: [Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info
- References: <20041222003609.19124.hjl@lucon.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From dberlin at gcc dot gnu dot org 2004-12-30 05:10 -------
Subject: Re: [4.0 regression] gcc generates incorrect
dwarf2 debug info
After talking with gdb folks and dwarf2 folks (who say this isn't the
actual bug, there
is some other gdb bug causing the crashes, because it doesn't depend on
the end and base addresses being different), i'm going to close this as
WONTFIX.
It's impossible for us to generate location lists with a end address >
base address, and nothing with any brainpower would depend on it :)
>
> ------- Additional Comments From hjl at lucon dot org 2004-12-30 03:38 -------
> While fixing the readelf bug:
>
> http://sources.redhat.com/bugzilla/show_bug.cgi?id=615
>
> I added a warning for bad location list. Even with your gcc patch applied, I
> still get
>
> [hjl@gnu-10 gcc]$ /export/build/linux/binutils-debug/build-i686-
> linux/binutils/readelf -w insn-preds.o > /dev/null
> readelf: Warning: Bad location list at 00000d3d from 00000a72 to 00000a72
>
> I will see what I can do with gdb.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19124