From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22069 invoked by alias); 4 May 2005 18:26:45 -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 21939 invoked from network); 4 May 2005 18:26:37 -0000 Received: from unknown (HELO romy.inter.net.il) (192.114.186.66) by sourceware.org with SMTP; 4 May 2005 18:26:37 -0000 Received: from zaretski (IGLD-80-230-9-69.inter.net.il [80.230.9.69]) by romy.inter.net.il (MOS 3.5.6-GR) with ESMTP id BDI55523 (AUTH halo1); Wed, 4 May 2005 21:25:53 +0300 (IDT) Date: Wed, 04 May 2005 18:26:00 -0000 From: "Eli Zaretskii" To: gdb-patches@sources.redhat.com Message-ID: <01c550d6$Blat.v2.4$874e3480@zahav.net.il> Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=ISO-8859-1 In-reply-to: <20050504180303.GZ24661@trixie.casa.cgf.cx> (message from Christopher Faylor on Wed, 4 May 2005 14:03:03 -0400) Subject: Re: [RFC] fullname attribute for GDB/MI stack frames Reply-to: Eli Zaretskii References: <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> <20050503213911.GB16440@trixie.casa.cgf.cx> <01c55061$Blat.v2.4$5a644e20@zahav.net.il> <20050504145200.GI24661@trixie.casa.cgf.cx> <20050504180303.GZ24661@trixie.casa.cgf.cx> X-SW-Source: 2005-05/txt/msg00128.txt.bz2 > Date: Wed, 4 May 2005 14:03:03 -0400 > From: Christopher Faylor > > >And then the question is whether it is correct to resolve d:foo > >etc. assuming thath the current drive and directories are identical to > >what they were when the source was compiled. Many projects use > >recursive Makefiles that cause the compiler change directories at > >will. > > I thought you were advocating that d:foo means "the current directory on > drive d:" no matter what it might have meant at compile time. I don't > see that we have any choice but to do anything but that and, apparently, > that is what lrealpath will do, as long as the environment is not > perturbed on XP. We have a choice: leave it as it is now. > So, why not just use lrealpath? Because it might be wrong, if the environment _was_ perturbed (as it frequently is, since the compiletr could have been in a totally different directory when it recorded d:foo). But if I still fail to convince you and others, go ahead and use lrealpath, since at least it doesn't do anything for the DJGPP port, so things will remain there as they are now.