From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17741 invoked by alias); 17 Apr 2009 17:07:07 -0000 Received: (qmail 17723 invoked by uid 22791); 17 Apr 2009 17:07:04 -0000 X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from eu1sys200aog106.obsmtp.com (HELO eu1sys200aog106.obsmtp.com) (207.126.144.121) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 17 Apr 2009 17:06:58 +0000 Received: from source ([164.129.1.35]) (using TLSv1) by eu1sys200aob106.postini.com ([207.126.147.11]) with SMTP ID DSNKSei3A+omCkNsrf586xH+HDQh37jIFCie@postini.com; Fri, 17 Apr 2009 17:06:56 UTC Received: from zeta.dmz-eu.st.com (ns2.st.com [164.129.230.9]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 80D65DA7D; Fri, 17 Apr 2009 17:04:59 +0000 (GMT) Received: from mail2.gnb.st.com (mail2.gnb.st.com [164.129.119.59]) by zeta.dmz-eu.st.com (STMicroelectronics) with ESMTP id E28194C7E0; Fri, 17 Apr 2009 17:06:09 +0000 (GMT) Received: from [164.129.122.46] (gnx2504.gnb.st.com [164.129.122.46]) by mail2.gnb.st.com (MOS 3.8.7a) with ESMTP id DCB49900 (AUTH lyon); Fri, 17 Apr 2009 19:06:13 +0200 (CEST) Message-ID: <49E8B701.1000402@st.com> Date: Fri, 17 Apr 2009 17:07:00 -0000 From: Christophe LYON User-Agent: Thunderbird 2.0.0.21 (X11/20090302) MIME-Version: 1.0 To: Joel Brobecker Cc: gdb-patches@sources.redhat.com Subject: Re: [PATCH] obvious pattern fix in gdb.base/step-line.exp References: <49CCDB3D.5010302@st.com> <20090327184726.GW9472@adacore.com> <49D083FB.6020108@st.com> <20090330170216.GB9472@adacore.com> <49D21E7E.8080708@st.com> <20090401183240.GD8766@adacore.com> <49D47C75.9000206@st.com> In-Reply-To: <49D47C75.9000206@st.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2009-04/txt/msg00450.txt.bz2 > >> I'm OK with leaving the testcase untouched if we don't need to. > OK. So I won't commit my patch, and fix the compiler instead. > I have been trying to fix the compiler so that it behaves like GCC (using 2 separate filenames for the actual source file and for the one provided with #line), but I get regressions later in step-line.exp. After dumping the debug_line info (with readelf and/or dwarfdump), I mostly noticed that the file number has changed according to the compiler fix. However, from GDB, using "maintenance print symbols", I noticed that quite a few lines have become "0" instead of meaningful values. In turn, I thinks this makes skip_prologue do something wrong. What I dont' understand currently is where those "0" line entries come from? Is there any verbose flag or maintenance command I could use to understand how the Dwarf debug_line info is parsed? Thanks, Christophe.