From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7755 invoked by alias); 8 Oct 2009 16:01:28 -0000 Received: (qmail 7323 invoked by uid 22791); 8 Oct 2009 16:01:27 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: sourceware.org Received: from sif.is.scarlet.be (HELO sif.is.scarlet.be) (193.74.71.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 08 Oct 2009 16:01:21 +0000 Received: from [172.17.1.10] (ip-81-11-246-100.dsl.scarlet.be [81.11.246.100]) by sif.is.scarlet.be (8.14.2/8.14.2) with ESMTP id n98G1EeE025646; Thu, 8 Oct 2009 18:01:15 +0200 Subject: Re: shared lib dos filename style - one more question From: Danny Backx Reply-To: danny.backx@scarlet.be To: Daniel Jacobowitz Cc: gdb-patches In-Reply-To: <20091007201145.GA21557@caradoc.them.org> References: <1253973110.10921.76.camel@pavilion> <1254946075.10921.178.camel@pavilion> <20091007201145.GA21557@caradoc.them.org> Content-Type: text/plain Date: Thu, 08 Oct 2009 16:01:00 -0000 Message-Id: <1255017831.10921.197.camel@pavilion> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-DCC-scarlet.be-Metrics: sif 20001; Body=3 Fuz1=3 Fuz2=3 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/msg00167.txt.bz2 On Wed, 2009-10-07 at 16:11 -0400, Daniel Jacobowitz wrote: > On Wed, Oct 07, 2009 at 10:07:55PM +0200, Danny Backx wrote: > > No reply to the message below. I'm including my current work now. Please > > comment. > > I've been staying out of this conversation because I don't have time > to discuss it properly, but I am still skeptical that this should ever > be a user setting - I've yet to see a plausible problem if we always > handled both styles of filesystem. > > If it does need to be a user setting, IMO it's acceptable to make > users set it in their .gdbinit or on the GDB command line. I'm sure that any effects of discouragement at my end are not the intention of this message :-) I'm perfectly willing to continue work on this (makes no sense to drop it now), but I'd like to know where to go from here. I'll ask some questions, maybe this'll give clarity : 1. If this work (or the way it's currently implemented) is questionable, then why have an effect on libiberty ? So : do we want this to go as far as extending libiberty slightly ? 2. This may all be much too complicated. Stuff the solution, make sure that forward slashes as well as backslashes as well as C:/ stuff are always supported. A very good or a very bad idea ? It would conflict with the "let's take this one step at a time" that someone told me. 3. Great idea. We'll get more of this soon. But let's not go further right now. Implement it as is, don't go the extra mile to re- evaluate everything if the user changes the variable in the middle of a session. What's good or bad about this ? 4. gdbserver is a bad idea. gdb shouldn't bother with debugging architectures that look different from the development host. I'm not sure what the question is here. These may be bad questions but it feels like the right time to stir up the discussion. Danny -- Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info