From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23146 invoked by alias); 22 Dec 2004 00:53:38 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 22941 invoked by uid 48); 22 Dec 2004 00:53:30 -0000 Date: Wed, 22 Dec 2004 00:53:00 -0000 Message-ID: <20041222005330.22940.qmail@sourceware.org> From: "hjl at lucon dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20041222003609.19124.hjl@lucon.org> References: <20041222003609.19124.hjl@lucon.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug debug/19124] [4.0 regression] gcc generates incorrect dwarf2 debug info X-Bugzilla-Reason: CC X-SW-Source: 2004-12/txt/msg03142.txt.bz2 List-Id: ------- Additional Comments From hjl at lucon dot org 2004-12-22 00:53 ------- A simple testcase: [hjl@gnu-10 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; } [hjl@gnu-10 gcc]$ ./xgcc -B./ -g -O -c foo.c -fomit-frame-pointer [hjl@gnu-10 gcc]$ readelf -w foo.o > /dev/null readelf: Error: Not enough comp units for .debug_loc section -fomit-frame-pointer may cause gcc to generate .debug_loc section gdb can't handle. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19124