From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2682 invoked by alias); 13 Oct 2009 15:51:47 -0000 Received: (qmail 2673 invoked by uid 22791); 13 Oct 2009 15:51:46 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 13 Oct 2009 15:51:40 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id BB7CD10EB5; Tue, 13 Oct 2009 15:53:30 +0000 (GMT) Received: from caradoc.them.org (209.195.188.212.nauticom.net [209.195.188.212]) by nan.false.org (Postfix) with ESMTP id F2A1910E84; Tue, 13 Oct 2009 15:53:29 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1Mxjey-00082Q-Gy; Tue, 13 Oct 2009 11:51:36 -0400 Date: Tue, 13 Oct 2009 15:51:00 -0000 From: Daniel Jacobowitz To: Joel Brobecker Cc: Danny Backx , gdb-patches Subject: Re: shared lib dos filename style - one more question Message-ID: <20091013155136.GA30684@caradoc.them.org> Mail-Followup-To: Joel Brobecker , Danny Backx , gdb-patches References: <1253973110.10921.76.camel@pavilion> <1254946075.10921.178.camel@pavilion> <20091007201145.GA21557@caradoc.them.org> <1255017831.10921.197.camel@pavilion> <20091009173650.GB5272@adacore.com> <1255114781.10921.217.camel@pavilion> <20091010021849.GC5272@adacore.com> <20091012204451.GA17607@caradoc.them.org> <20091013052101.GI5272@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091013052101.GI5272@adacore.com> User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2009-10/txt/msg00273.txt.bz2 On Mon, Oct 12, 2009 at 10:21:01PM -0700, Joel Brobecker wrote: > > There's nothing straightforward that this latter approach could do for > > case-sensitivity problems, though - is there? I'd prefer not to > > completely rule out handling this case. > > Hmmm, I was indeed carefully side-stepping this issue, busted :). > I was hoping that this wasn't going to matter in practice... I've worked with a build system (for a mobile phone OS) that uppercase all filenames halfway through the build process. So which case you get in debug info is pretty hard to predict. -- Daniel Jacobowitz CodeSourcery