From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23237 invoked by alias); 6 Dec 2005 20:17:24 -0000 Received: (qmail 23230 invoked by uid 22791); 6 Dec 2005 20:17:24 -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 20:17:22 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1EjjFX-0002Pd-P7 for gdb@sourceware.org; Tue, 06 Dec 2005 15:17:19 -0500 Date: Tue, 06 Dec 2005 20:17:00 -0000 From: Daniel Jacobowitz To: gdb@sourceware.org Subject: Re: Filename with "./" in breakpoint command Message-ID: <20051206201719.GA9140@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> 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/msg00063.txt.bz2 On Tue, Dec 06, 2005 at 10:11:21PM +0200, Eli Zaretskii wrote: > I didn't say that "./foo.c" shouldn't resolve to the file in the > current working directory, I'm saying that it is not, IMHO, a good > solution of the original problem. > > The original problem was _not_ that "./foo.c" didn't do what the user > expected; "./foo.c" was an attempt of _solving_ a problem. And the > problem the OP tried to solve was that there were several source files > linked into the executable, each one in its own directory. > > I don't like telling the user to go to some directory to solve that > original problem. For starters, it requires the user to type the full > name of the directory, which is almost like asking them to type the > full file name of the source file. Great - then we all agree, except for a tangent on the meaning of "original problem" ;-) I was responding to the question Vladimir asked at the start of the thread: http://sourceware.org/ml/gdb/2005-12/msg00035.html > I'd prefer to have a better solution to the original problem. We do; use full pathnames. Vladimir already said he was fixing kdevelop to not use ./, so I think that's well in hand. "info sources" and the MI fullname field will both show the absolute pathname, including the compilation directory. -- Daniel Jacobowitz CodeSourcery, LLC