From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1499 invoked by alias); 23 Aug 2005 14:49:54 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 838 invoked by uid 22791); 23 Aug 2005 14:49:14 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Tue, 23 Aug 2005 14:49:14 +0000 Received: from drow by nevyn.them.org with local (Exim 4.52) id 1E7a5P-0007Gj-2L; Tue, 23 Aug 2005 10:49:11 -0400 Date: Tue, 23 Aug 2005 14:49:00 -0000 From: Daniel Jacobowitz To: Craig Jeffree , gdb@sources.redhat.com Subject: Re: trouble locating source files through relative paths Message-ID: <20050823144911.GA27857@nevyn.them.org> Mail-Followup-To: Craig Jeffree , gdb@sources.redhat.com References: <1124436292.3582.64.camel@norman> <20050819124329.GA18911@white> <1124773410.3749.38.camel@norman> <20050823113138.GA27899@white> <20050823114028.GB27899@white> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050823114028.GB27899@white> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-08/txt/msg00088.txt.bz2 On Tue, Aug 23, 2005 at 07:40:28AM -0400, Bob Rossi wrote: > On Tue, Aug 23, 2005 at 07:31:38AM -0400, Bob Rossi wrote: > > On Tue, Aug 23, 2005 at 03:03:29PM +1000, Craig Jeffree wrote: > > > On Fri, 2005-08-19 at 08:43 -0400, Bob Rossi wrote: > > > > What was the 'dir' command that you issued? What compiler are you using? > > > > Do you know what debug format you are using? (stabs or dwarf)? > > > > > > The dir command that I issued was: > > > (gdb) dir /staff/taam/taam/bin/x86-Linux/nostrip/ > > > Source directories searched: /staff/taam/taam/bin/x86-Linux/nostrip: > > > $cdir:$cwd > > > > > > I'm using gcc 3.2.3 with the default debug format for x86-Linux (dwarf2 > > > I believe). > > > > Is this problem reproducable in a small example? > > Geez, actually, I did just reproduce the problem. It seems that the only > current solution to get it to work is to do as you said, put the path to > where the include file is, not to where the relative path to it is. > > I'll look into this. Great! Yeah, I've seen this one before - I posted a (less thorough!) analysis of it back when openp.exp was posted. I would _love_ to see this fixed. IIRC, you can also trigger it by using -I../include and trying to list code in a header file; I had a test case in the gdb-patches archives somewhere but never had time to track it down. -- Daniel Jacobowitz CodeSourcery, LLC