From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29275 invoked by alias); 3 Mar 2011 13:21:00 -0000 Received: (qmail 29265 invoked by uid 22791); 3 Mar 2011 13:20:59 -0000 X-SWARE-Spam-Status: No, hits=-1.1 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST X-Spam-Check-By: sourceware.org Received: from mail-qw0-f41.google.com (HELO mail-qw0-f41.google.com) (209.85.216.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 03 Mar 2011 13:20:54 +0000 Received: by qwd7 with SMTP id 7so1040817qwd.0 for ; Thu, 03 Mar 2011 05:20:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.224.9.65 with SMTP id k1mr1057809qak.37.1299158452554; Thu, 03 Mar 2011 05:20:52 -0800 (PST) Received: by 10.229.89.197 with HTTP; Thu, 3 Mar 2011 05:20:52 -0800 (PST) In-Reply-To: References: <201103031214.p23CEj4Z010743@glazunov.sibelius.xs4all.nl> Date: Thu, 03 Mar 2011 13:21:00 -0000 Message-ID: Subject: Re: [patch gdb]: Fix some DOS-path related issues in gdb From: Kai Tietz To: Eli Zaretskii Cc: mark.kettenis@xs4all.nl, gdb@sourceware.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-03/txt/msg00034.txt.bz2 2011/3/3 Eli Zaretskii : >> Date: Thu, 3 Mar 2011 13:50:40 +0100 >> From: Kai Tietz >> Cc: gdb@sourceware.org >> >> hmm, I admit that it is pretty unlikely that *nix-nat parts are used >> with DOS-style paths. Nevertheless on cross-compiling from windows to >> *nix such paths can happen easily. > > How can this happen, even for cross compilation? =A0Can you describe a > use-case? The debugging information (profiling, etc) are always using host's file-names. So if you create a cross-compiler, the file-name/path-information stored are always that one of the host-system. Not of the target. There is a need of having here some additional mapping features, but this is for now not addressed by this patch. For example, use a cross-compiler for windows-native on an unix-OS and build an application with profiling and/or debugging. Then try to debug/profile this app on a native windows host. You will notice that filenames/paths are that one from the unix-OS and therefore are pretty unusable on native Windows. (The other way around is of course the same). Kai