[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- Additional Comments From dberlin at gcc dot gnu dot org 2005-01-20 20:15 --- Fixed -- What|Removed |Added Status|ASSIGNED|RESOLVED

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-01-20 20:09 --- Subject: Bug 19124 CVSROOT:/cvs/gcc Module name:gcc Changes by: [EMAIL PROTECTED] 2005-01-20 20:09:23 Modified files: gcc: ChangeLog dwarf2out.c Log message:

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- Additional Comments From hjl at lucon dot org 2005-01-10 22:37 --- readelf may have false postives on [without DW_AT_frame_base]. I will leave it there. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19124

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- Additional Comments From hjl at lucon dot org 2005-01-10 18:55 --- "[without DW_AT_frame_base]" is very much informational and it may not be correct. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19124

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- Additional Comments From dberlin at gcc dot gnu dot org 2005-01-10 18:32 --- The patch is correct, the code printing "without DW_AT_frame_base" is wrong. Note that while the immediate container of the variable, the DW_TAG_inlined_subroutine, does not have a frame_base attribute, *it

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- Additional Comments From dberlin at gcc dot gnu dot org 2005-01-10 16:45 --- Subject: Re: [4.0 regression] gcc generates incorrect dwarf2 debug info On Mon, 2005-01-10 at 16:39 +, hjl at lucon dot org wrote: > There are still: > > 29df 2cbe 2ccc (DW_O

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- Additional Comments From ac131313 at redhat dot com 2005-01-04 20:07 --- (In reply to comment #5) > If gdb can't handle var-tracking, it should be fixed there, and not > be disabeld in gcc. Correct. GCC shouldn't hold back features due to a lack of support in GDB. See also http://so

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- Additional Comments From dberlin at gcc dot gnu dot org 2005-01-02 20:29 --- Patch coming. This is also a latent bug forever in gcc. We've been generating fbreg for a lot of things we shouldn't, we just never noticed before now because it didn't try to evaluate them at runtime unles

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- Additional Comments From hjl at lucon dot org 2004-12-30 21:01 --- insn-preds.o was compiled with stage2/xgcc -Bstage2/ -B/usr/gcc-4.0/i686-pc-linux-gnu/bin/ -c -O2 -g -fomit- frame-pointer -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes - Wmissing-prototypes -pedantic -Wno

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

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

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- 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 [EMAIL PROTECTED] gcc]$ /export/build/linux

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- Additional Comments From dberlin at dberlin dot org 2004-12-28 18:49 --- Subject: Re: [4.0 regression] gcc generates incorrect dwarf2 debug info On Tue, 2004-12-28 at 18:37 +, hjl at lucon dot org wrote: > --- Additional Comments From hjl at lucon dot org 2004-12-

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- Additional Comments From hjl at lucon dot org 2004-12-28 18:37 --- With the patch applied, gdb 6.3 still dumps core. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19124

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- Additional Comments From pinskia at gcc dot gnu dot org 2004-12-28 02:34 --- Patch here: . -- What|Removed |Added

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- Additional Comments From dberlin at gcc dot gnu dot org 2004-12-26 00:56 --- The bug is in both readelf and a gcc bug. The warning in readelf is a bug. One can see by looking at the assembly that their is exactly one debug_loc section, and exactly one debug_info section, in the obje

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- Additional Comments From steven at gcc dot gnu dot org 2004-12-22 13:07 --- If gdb can't handle var-tracking, it should be fixed there, and not be disabeld in gcc. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19124

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- Additional Comments From pinskia at gcc dot gnu dot org 2004-12-22 01:33 --- One more thing, we now produce variable tracking which I hear don't get along well with gdb or readelf so I assume -fno-var-tracking will get rid of the seg fault but at that point, the seg fault becomes

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- Additional Comments From pinskia at gcc dot gnu dot org 2004-12-22 01:11 --- Are you sure that this is not a gdb bug? Also gdb should not being crashing did you at least file a gdb bug? also is this a readelf bug? -- What|Removed |Added

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- Additional Comments From hjl at lucon dot org 2004-12-22 01:09 --- It has nothing to do with -fomit-frame-pointer: [EMAIL PROTECTED] gcc]$ cat foo.c extern char *array; void foo (unsigned int array_members) { unsigned int i; for (i = 0; i < array_members; i++) array[i] = i %

[Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info

--- Additional Comments From hjl at lucon dot org 2004-12-22 00:53 --- A simple testcase: [EMAIL PROTECTED] gcc]$ cat foo.c extern char *array; void foo (unsigned int array_members) { unsigned int i; for (i = 0; i < array_members; i++) array[i] = i % 128; } [EMAIL PROTECTED] gcc]