From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12962 invoked by alias); 19 May 2010 15:40:39 -0000 Received: (qmail 12772 invoked by uid 48); 19 May 2010 15:40:07 -0000 Date: Wed, 19 May 2010 15:40:00 -0000 Message-ID: <20100519154007.12771.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug debug/44113] bad debugging information for unrolled loops In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "andi-gcc at firstfloor dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-05/txt/msg02073.txt.bz2 ------- Comment #6 from andi-gcc at firstfloor dot org 2010-05-19 15:40 ------- Jakub, are you saying this should be fixed in gdb? How could gdb detect this case? If gcc emitted another .loc like you said couldn't gdb check for this? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44113