From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14833 invoked by alias); 15 May 2008 19:18:40 -0000 Received: (qmail 13407 invoked by uid 22791); 15 May 2008 19:17:06 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 15 May 2008 19:16:45 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 0DD55983D6; Thu, 15 May 2008 19:16:44 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id B26549830E; Thu, 15 May 2008 19:16:43 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1JwiwU-00048j-ED; Thu, 15 May 2008 15:16:42 -0400 Date: Thu, 15 May 2008 19:44:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: aristovski@qnx.com, gdb-patches@sources.redhat.com Subject: Re: [RFC] new substitute path when loading feature Message-ID: <20080515191642.GA15892@caradoc.them.org> Mail-Followup-To: Eli Zaretskii , aristovski@qnx.com, gdb-patches@sources.redhat.com References: <20080513190818.GA13776@caradoc.them.org> <4829E7DA.3010606@qnx.com> <20080513192041.GA14593@caradoc.them.org> <20080515160551.GA24101@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes 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: 2008-05/txt/msg00482.txt.bz2 On Thu, May 15, 2008 at 09:55:05PM +0300, Eli Zaretskii wrote: > Well, the patch will certainly work with DOS-ish file names on a Posix > host, but I'm worried about breaking file names that are perfectly > valid on Posix filesystems, but which just happen to use colons and > backslashes. I agree that a probability of meeting such file names on > Posix platforms is miniscule, but this patch leaves the user no fire > escape whatsoever when she does meet them. > > Can we please augment this with some minimal band-aid for when > backslashes and colons are literally used in a file name? Something > like a user option to disable this feature and use normal Posix > file-name syntax? I figure this would be enough, since mixing object > files compiled on Posix and Windows platforms should be _really_ rare. To have trouble I think you'd need to have two files in a project whose name only differed by slashes: e.g. "a\b.c" and directory "a" and "a/b.c". Mistakenly thinking a path is relative might cause some problems but I can't think of how they would manifest. I'm happy to add the band-aid; do you have an idea of what to call it? set strict-filenames? > Will this work if the file name is encoded in UTF-8 or some other > multi-byte encoding, btw? We do want to support those, don't we? The POSIX parts will work in UTF-8, since no multi-byte UTF-8 characters contain printable 7-bit ASCII. Other encodings, or with the tolower check, I don't know. -- Daniel Jacobowitz CodeSourcery