From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31056 invoked by alias); 24 Jun 2006 07:11:06 -0000 Received: (qmail 31048 invoked by uid 22791); 24 Jun 2006 07:11:05 -0000 X-Spam-Check-By: sourceware.org Received: from nile.gnat.com (HELO nile.gnat.com) (205.232.38.5) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 24 Jun 2006 07:11:02 +0000 Received: from localhost (localhost [127.0.0.1]) by filtered-nile.gnat.com (Postfix) with ESMTP id 2EDE948CBDF; Sat, 24 Jun 2006 03:11:00 -0400 (EDT) Received: from nile.gnat.com ([127.0.0.1]) by localhost (nile.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 09430-02-7; Sat, 24 Jun 2006 03:11:00 -0400 (EDT) Received: from takamaka.act-europe.fr (s142-179-108-108.bc.hsia.telus.net [142.179.108.108]) by nile.gnat.com (Postfix) with ESMTP id D3C5748CBD6; Sat, 24 Jun 2006 03:10:59 -0400 (EDT) Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 9602447E7F; Sat, 24 Jun 2006 00:10:58 -0700 (PDT) Date: Sat, 24 Jun 2006 07:15:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: gdb@sources.redhat.com Subject: Re: Should "dir" override the full path encoded in debug info? Message-ID: <20060624071058.GD22750@adacore.com> References: <20060623201019.GX22750@adacore.com> <20060624065920.GB22750@adacore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-06/txt/msg00206.txt.bz2 > > (gdb) list foo.c:1 > > warning: Source file is more recent than executable. > > What happens if you remove or rename the file foo.c in the original > location? GDB finds the file in dup/. But in our case, we cannot touch the file in the original location, since the testsuite engine needs it for the next testing batch. Building in a different location is not an option either because we want to only recompile the files we touched (and their dependencies). So basically, at this time, it appears that we're stuck. -- Joel