From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4925 invoked by alias); 18 Sep 2009 16:12:04 -0000 Received: (qmail 4916 invoked by uid 22791); 18 Sep 2009 16:12:03 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from eu1sys200aog107.obsmtp.com (HELO eu1sys200aog107.obsmtp.com) (207.126.144.123) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 18 Sep 2009 16:11:58 +0000 Received: from source ([164.129.1.35]) (using TLSv1) by eu1sys200aob107.postini.com ([207.126.147.11]) with SMTP ID DSNKSrOxSwtgmmN6OZX37k7gdB90BoK2t/Pm@postini.com; Fri, 18 Sep 2009 16:11:58 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 44462177 for ; Fri, 18 Sep 2009 16:11:55 +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 08FEC4C2D5 for ; Fri, 18 Sep 2009 16:11:54 +0000 (GMT) Received: from [164.129.122.40] (gnx2504.gnb.st.com [164.129.122.40]) by mail2.gnb.st.com (MOS 3.8.7a) with ESMTP id DGB64370 (AUTH lyon); Fri, 18 Sep 2009 18:12:59 +0200 (CEST) Message-ID: <4AB3B14A.6000405@st.com> Date: Fri, 18 Sep 2009 16:12:00 -0000 From: Christophe LYON User-Agent: Thunderbird 2.0.0.23 (X11/20090812) MIME-Version: 1.0 To: gdb@sourceware.org Subject: GDB cannot find line info Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-09/txt/msg00227.txt.bz2 Hello, I have found a bug in our compiler (Open64 for ST200), which I have fixed to make it correctly output the directory table related to debug_line info. But now, I have many regressions in the GDB testsuite (6.8), the first one being in break.exp: now the command "break break.c:103" returns 'No line 103 in file "break.c"' I have dumped the dwarf debug_line info with 'dwarfdump -l' and 'readelf -wl', but could not find anything suspect: - with dwarfdump, the only difference is in the directory path - with readelf, the directory tables contain one more entry (absolute path to gdb.base) and the file table has dir numbers updated accordingly. (obviously, the length and offset of the corresponding sections are different) Is there any GDB internal command I could use to understand the problem? Thanks, Christophe.