From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15956 invoked by alias); 21 Jan 2004 14:09:33 -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 15948 invoked from network); 21 Jan 2004 14:09:32 -0000 Received: from unknown (HELO mainserv.chemcon.no) (193.75.7.58) by sources.redhat.com with SMTP; 21 Jan 2004 14:09:32 -0000 Received: from cc-intern01 (cc-intern01.chemcon.nett [192.168.1.2]) by mainserv.chemcon.no (8.12.8/8.12.8) with ESMTP id i0LE9D6H010678 for ; Wed, 21 Jan 2004 15:09:28 +0100 Subject: gdb has problems finding my sources From: Tarjei Knapstad To: gdb Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Wed, 21 Jan 2004 14:09:00 -0000 Message-Id: <1074694168.24023.73.camel@cc-intern01> Mime-Version: 1.0 X-SW-Source: 2004-01/txt/msg00235.txt.bz2 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. Thanks in advance, -- Tarjei Knapstad