From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27243 invoked by alias); 16 May 2008 08:15:14 -0000 Received: (qmail 26814 invoked by uid 22791); 16 May 2008 08:15:05 -0000 X-Spam-Check-By: sourceware.org Received: from mtaout6.012.net.il (HELO mtaout6.012.net.il) (84.95.2.16) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 16 May 2008 08:14:46 +0000 Received: from HOME-C4E4A596F7 ([83.130.255.47]) by i-mtaout6.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0K0Y00587CVPC670@i-mtaout6.012.net.il> for gdb-patches@sources.redhat.com; Fri, 16 May 2008 11:28:37 +0300 (IDT) Date: Fri, 16 May 2008 15:27:00 -0000 From: Eli Zaretskii Subject: Re: [RFC] new substitute path when loading feature In-reply-to: <200805152004.m4FK4n82007876@brahms.sibelius.xs4all.nl> X-012-Sender: halo1@inter.net.il To: Mark Kettenis Cc: drow@false.org, aristovski@qnx.com, gdb-patches@sources.redhat.com Reply-to: Eli Zaretskii Message-id: References: <20080513190818.GA13776@caradoc.them.org> <4829E7DA.3010606@qnx.com> <20080513192041.GA14593@caradoc.them.org> <20080515160551.GA24101@caradoc.them.org> <20080515191642.GA15892@caradoc.them.org> <20080515193513.GA17156@caradoc.them.org> <482C91AA.30903@qnx.com> <20080515194418.GA17618@caradoc.them.org> <200805152004.m4FK4n82007876@brahms.sibelius.xs4all.nl> 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/msg00497.txt.bz2 > Date: Thu, 15 May 2008 22:04:49 +0200 (CEST) > From: Mark Kettenis > CC: aristovski@qnx.com, gdb-patches@sources.redhat.com, eliz@gnu.org > > > set support-dos-filenames (on|off|auto) > > > > Auto would be case sensitive on POSIX hosts, on wouldn't, auto would > > be the default. > > Sorry, but I think this really is a bad idea. For a native debugger > on a POSIX system I really don't want the oddities of dos-like filenames. Well, then you could set this option to never do that, couldn't you? The problem is real, Mark. Why can't we give our users a way to cope with it, as an option?