From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25554 invoked by alias); 4 May 2005 13:51:33 -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 25406 invoked from network); 4 May 2005 13:51:24 -0000 Received: from unknown (HELO lakermmtao05.cox.net) (68.230.240.34) by sourceware.org with SMTP; 4 May 2005 13:51:24 -0000 Received: from white ([68.9.64.121]) by lakermmtao05.cox.net (InterMail vM.6.01.04.00 201-2131-118-20041027) with ESMTP id <20050504135124.HKUZ13442.lakermmtao05.cox.net@white> for ; Wed, 4 May 2005 09:51:24 -0400 Received: from bob by white with local (Exim 3.35 #1 (Debian)) id 1DTKHa-00079s-00 for ; Wed, 04 May 2005 09:51:22 -0400 Date: Wed, 04 May 2005 13:51:00 -0000 From: Bob Rossi To: gdb-patches@sources.redhat.com Subject: Re: [RFC] fullname attribute for GDB/MI stack frames Message-ID: <20050504135122.GA27415@white> Mail-Followup-To: gdb-patches@sources.redhat.com 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> <20050503194856.GA4477@nevyn.them.org> <01c55021$Blat.v2.4$520aa7a0@zahav.net.il> <20050504133437.GA10578@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050504133437.GA10578@nevyn.them.org> User-Agent: Mutt/1.3.28i X-SW-Source: 2005-05/txt/msg00112.txt.bz2 > > > We can't show the user the file, but we can use it to unambiguously > > > place a breakpoint in the correct file. > > > > The same can be said about "\abc" or "d:foo". > > No, I don't think it can. The difference between an absolute path and > a partially relative path is that an absolute path has no implicit > information. If GDB reports that one file includes a header c:\abc and > another includes \abc, the front end has to guess whether GDB considers > those the same file or not. This is very true. This will break CGDB for instance. It use's the fullname as a unique key to a file. If GDB says that c:\abc has 2 breakpoints and \abc has 1, CGDB will have 2 source files the user can choose and each will contain it's own breakpoints. It should just think there is 1 file. What would 'info sources' do in this case anyways? Thanks, Bob Rossi