From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30257 invoked by alias); 21 Jan 2004 15:12:35 -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 30249 invoked from network); 21 Jan 2004 15:12:34 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 21 Jan 2004 15:12:34 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1AjK1x-0000HN-GH; Wed, 21 Jan 2004 10:12:33 -0500 Date: Wed, 21 Jan 2004 15:12:00 -0000 From: Daniel Jacobowitz To: Tarjei Knapstad Cc: gdb Subject: Re: gdb has problems finding my sources Message-ID: <20040121151232.GA1013@nevyn.them.org> Mail-Followup-To: Tarjei Knapstad , gdb References: <1074694168.24023.73.camel@cc-intern01> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1074694168.24023.73.camel@cc-intern01> User-Agent: Mutt/1.5.1i X-SW-Source: 2004-01/txt/msg00236.txt.bz2 On Wed, Jan 21, 2004 at 03:09:13PM +0100, Tarjei Knapstad wrote: > I've got a C++ test suite project that includes headers from and links > with static libraries from another project which resides in a different > directory tree (also pure C++). I'm using the current Fedora Core 2 > snapshot of gdb (gdb-6.0post-0.20031117.7 from 08-01-2004), but I've got > the same problems with either 5.2 or 5.3. > > When debugging this testsuite gdb apparently has problems when I try to > step into (template) functions contained in certain header files. The > headers in question contain only template code which is used and linked > into the testsuite application. gdb just gives me "xxx yyy.h: File or > directory not found" where xxx is a line number and yyy.h is the header > file in question. > > If I add the source directory for yyy.h explicitly from gdb using the > 'dir' command it works, but I don't understand why I should have to do > that - it works perfectly with for instance the Boost and STL headers. > The other problems with adding the searchpath explicitly is that I'm > using gdb from within KDevelop where I don't have access to the gdb > commandline, as well as the fact that it's a great nusiance to have to > add the dirs (there are potentially lots) each time I run the debugger. > > I've reproduced this exact same behaviour using gdb from the commandline > so I don't think it's KDevelop's fault. > > Is there anyone who could provide me with any pointers wrt. how I can > possibly fix this? Any help getting this sorted would be much > appreciated. If you can provide a small testcase for the problem, we can investigate some more. I'm not sure from your description what could be broken. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer