From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14427 invoked by alias); 4 Dec 2001 22:24:19 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 14391 invoked from network); 4 Dec 2001 22:24:15 -0000 Received: from unknown (HELO geoffk.org) (205.180.231.50) by sources.redhat.com with SMTP; 4 Dec 2001 22:24:15 -0000 Received: (from geoffk@localhost) by geoffk.org (8.9.3/8.9.3) id OAA11668; Tue, 4 Dec 2001 14:23:52 -0800 To: Neil Booth CC: gcc@gcc.gnu.org Subject: Re: problems debugging gcc References: <200112041958.LAA06265@kankakee.wrs.com> <20011204203454.A20475@daikokuya.demon.co.uk> Reply-to: Geoff Keating From: Geoff Keating Date: Tue, 04 Dec 2001 14:24:00 -0000 In-Reply-To: Neil Booth's message of "Tue, 4 Dec 2001 20:34:54 +0000" Message-ID: X-Mailer: Gnus v5.5/Emacs 20.3 X-SW-Source: 2001-12/txt/msg00181.txt.bz2 Neil Booth writes: > mike stump wrote:- > > > Yes. Step through bison.simple a couple hundred times, and you'll > > discover that most of the time, it spends it's time in about two to > > four places you care about. One place, is dispatching to actions. It > > can be felt, by noticing the line (at least in bison 1.25): > > Have you noticed that you often get the debugger trying to step to a > line in bison.simple that is in fact in parse.y, and complaining about > a line out range? > > This happens to me very frequently; I have no idea what causes it. I > have a sneaking suspicion that this GCC bug is what the original post > was about, though I'm not sure. There's a bug in cc1: it doesn't store file names for statements, only line numbers, and so debugging information for functions that have lines from multiple files is often wrong. -- - Geoffrey Keating