From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4813 invoked by alias); 4 May 2005 04:08:16 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 4453 invoked from network); 4 May 2005 04:08:10 -0000 Received: from unknown (HELO legolas.inter.net.il) (192.114.186.24) by sourceware.org with SMTP; 4 May 2005 04:08:10 -0000 Received: from zaretski (IGLD-80-230-71-109.inter.net.il [80.230.71.109]) by legolas.inter.net.il (MOS 3.5.6-GR) with ESMTP id EHD41177 (AUTH halo1); Wed, 4 May 2005 07:08:05 +0300 (IDT) Date: Wed, 04 May 2005 04:08:00 -0000 From: "Eli Zaretskii" To: gdb-patches@sources.redhat.com Message-ID: <01c5505e$Blat.v2.4$ae323100@zahav.net.il> Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=ISO-8859-1 In-reply-to: <20050503221340.GD16440@trixie.casa.cgf.cx> (message from Christopher Faylor on Tue, 3 May 2005 18:13:40 -0400) Subject: Re: [RFC] fullname attribute for GDB/MI stack frames Reply-to: Eli Zaretskii References: <01c54f50$Blat.v2.4$29b171c0@zahav.net.il> <20050502195515.GA10429@nevyn.them.org> <01c54f57$Blat.v2.4$4c163500@zahav.net.il> <20050502204859.GA6090@nevyn.them.org> <01c54f91$Blat.v2.4$f6e0b160@zahav.net.il> <20050503034604.GA437@nevyn.them.org> <01c55017$Blat.v2.4$3cb51f20@zahav.net.il> <20050503195650.GD25356@white> <01c55025$Blat.v2.4$00e755e0@zahav.net.il> <20050503213943.GG25356@white> <20050503221340.GD16440@trixie.casa.cgf.cx> X-SW-Source: 2005-05/txt/msg00103.txt.bz2 > Date: Tue, 3 May 2005 18:13:40 -0400 > From: Christopher Faylor > > Wouldn't it make more sense to fix the fullpath machinery? The fullpath machinery is fine, it doesn't need any fixing. Please, let's not break something that works just because some test case doesn't seem 100% correct. Let's keep things in the right perspective here. The fullpath machinery was invented to let GDB process file names for its internal purposes, and it does its job well, because for those purposes, treating d:foo as absolute file names is _exactly_ right.