From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23427 invoked by alias); 22 Jan 2004 17:26:08 -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 23406 invoked from network); 22 Jan 2004 17:26:05 -0000 Received: from unknown (HELO bilbo.inter.net.il) (192.114.186.18) by sources.redhat.com with SMTP; 22 Jan 2004 17:26:05 -0000 Received: from zaretski ([80.230.144.144]) by bilbo.inter.net.il (Mirapoint Messaging Server MOS 3.3.8-GR) with ESMTP id CGL28993; Thu, 22 Jan 2004 19:25:52 +0200 (IST) Date: Thu, 22 Jan 2004 17:26:00 -0000 From: "Eli Zaretskii" To: Gernot Hillier Message-Id: <1659-Thu22Jan2004192206+0200-eliz@elta.co.il> CC: gdb@sources.redhat.com In-reply-to: <200401221601.17594.gernot.hillier@siemens.com> (message from Gernot Hillier on Thu, 22 Jan 2004 16:01:14 +0100) Subject: Re: handling of absolute source file paths (feature wish/implementation idea) Reply-to: Eli Zaretskii References: <200401221601.17594.gernot.hillier@siemens.com> X-SW-Source: 2004-01/txt/msg00248.txt.bz2 > From: Gernot Hillier > Date: Thu, 22 Jan 2004 16:01:14 +0100 > > 3. Implement a new setting "source-absolute-prefix" (analog to the already > existing "solib-absolute-prefix") which allows the user to set a prefix for > given absolute source code paths. I like this suggestion the best. It does exactly what you need here: allow the source directory tree to be moved deeper in the hierarchy. Your other suggestion, searching the source path for relative file names, sounds like an ad-hoc hack to me.