From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-35642-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 4486 invoked by alias); 21 Sep 2009 07:45:57 -0000
Received: (qmail 4477 invoked by uid 22791); 21 Sep 2009 07:45:57 -0000
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 	tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
Received: from mail-px0-f193.google.com (HELO mail-px0-f193.google.com) (209.85.216.193)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 21 Sep 2009 07:45:53 +0000
Received: by pxi31 with SMTP id 31so2153303pxi.19         for <gdb@sourceware.org>; Mon, 21 Sep 2009 00:45:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.115.24.10 with SMTP id b10mr7981240waj.127.1253519151334; Mon,  	21 Sep 2009 00:45:51 -0700 (PDT)
Date: Mon, 21 Sep 2009 07:45:00 -0000
Message-ID: <a0319f700909210045q4b674e77tfee6b082babe379@mail.gmail.com>
Subject: Re: GDB cannot find line info
From: Robert Bu <robert.bu@gmail.com>
To: christophe.lyon@st.com
Cc: gdb@sourceware.org
Content-Type: text/plain; charset=ISO-8859-1
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2009-09/txt/msg00260.txt.bz2

Hi Christophe,

Maybe you can try the CVS head or the 7.0 preview. I've once met the
same problem. And the problem is gone in CVS. Actually the problem is
fixed by the newly added function "watch_main_source_file_lossage
(void)" in buildsym.c

Robert.

>
>
> 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.
>