From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22813 invoked by alias); 4 Mar 2011 08:23:14 -0000 Received: (qmail 22796 invoked by uid 22791); 4 Mar 2011 08:23:13 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 04 Mar 2011 08:23:08 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 65EED2BAEAF; Fri, 4 Mar 2011 03:23:06 -0500 (EST) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id LcIk3rOkTEQl; Fri, 4 Mar 2011 03:23:06 -0500 (EST) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 965AA2BAEAE; Fri, 4 Mar 2011 03:23:05 -0500 (EST) Received: by joel.gnat.com (Postfix, from userid 1000) id 8D4B21459AD; Fri, 4 Mar 2011 12:22:47 +0400 (RET) Date: Fri, 04 Mar 2011 08:23:00 -0000 From: Joel Brobecker To: Vladimir Simonov Cc: Kai Tietz , Pedro Alves , gdb-patches@sourceware.org, Eli Zaretskii Subject: Re: [patch gdb]: Fix some DOS-path related issues in gdb Message-ID: <20110304082247.GF30306@adacore.com> References: <201103031609.43441.pedro@codesourcery.com> <201103031642.28783.pedro@codesourcery.com> <4D708E58.6080702@sw.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D708E58.6080702@sw.ru> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-03/txt/msg00275.txt.bz2 > If the main problem is in mapping absolute DOS paths to Linux ones then > the simplest solution is creation appropriate symbolic links > on Linux side. I mean that using symlink D: pointed on some directory > you can simulate any DOS path. I'm using this approach for many years... On my end of things, this is not what I was concerned about (it sounds like debugging a program on a different system than the one it was built on - I assumed that build and debug systems were the same). For your case, you can perhaps have a look at "set substitute-path" (or something like that). -- Joel