From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26222 invoked by alias); 4 Jan 2005 20:07:10 -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 25961 invoked by uid 48); 4 Jan 2005 20:07:04 -0000 Date: Tue, 04 Jan 2005 20:07:00 -0000 Message-ID: <20050104200704.25960.qmail@sourceware.org> From: "ac131313 at redhat dot com" 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: 2005-01/txt/msg00376.txt.bz2 List-Id: ------- 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://sources.redhat.com/ml/gdb/2004-11/msg00085.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19124