From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24937 invoked by alias); 6 Dec 2005 21:09:06 -0000 Received: (qmail 24818 invoked by uid 22791); 6 Dec 2005 21:09:05 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Tue, 06 Dec 2005 21:09:02 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1Ejk3Y-0002ok-Ji for gdb@sourceware.org; Tue, 06 Dec 2005 16:09:00 -0500 Date: Tue, 06 Dec 2005 21:09:00 -0000 From: Daniel Jacobowitz To: gdb@sourceware.org Subject: Re: Filename with "./" in breakpoint command Message-ID: <20051206210900.GA10747@nevyn.them.org> Mail-Followup-To: gdb@sourceware.org References: <200512050953.01350.ghost@cs.msu.su> <20051205185556.GA9808@nevyn.them.org> <20051206045518.GA23837@nevyn.them.org> <20051206201719.GA9140@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-12/txt/msg00065.txt.bz2 On Tue, Dec 06, 2005 at 11:02:20PM +0200, Eli Zaretskii wrote: > > Date: Tue, 6 Dec 2005 15:17:19 -0500 > > From: Daniel Jacobowitz > > > > > I'd prefer to have a better solution to the original problem. > > > > We do; use full pathnames. > > I thought Vladimir didn't like it (and neither do I, frankly). What else is there? Not a rhetorical question, I just don't see any alternative. Well, we could invent unique identifers "gdb-file-1186", "gdb-file-1187". Vladimir's original report is for communication from an IDE to GDB. "Find the best match" and "ask the user" aren't very helpful; the IDE needs to unambiguously specify what file it's already opened and is showing to the user, in a way that GDB can understand precisely what file is meant. Absolute pathnames seem awfully convenient for that. For a user typing "break foo.c:54" we've already agreed on a more useful behavior - though no promises when it will be implemented! -- Daniel Jacobowitz CodeSourcery, LLC