From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18447 invoked by alias); 7 Dec 2005 16:46:44 -0000 Received: (qmail 18439 invoked by uid 22791); 7 Dec 2005 16:46:43 -0000 X-Spam-Check-By: sourceware.org Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 07 Dec 2005 16:46:41 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Ek2OI-0000vF-5K for gdb@sources.redhat.com; Wed, 07 Dec 2005 17:43:38 +0100 Received: from zigzag.lvk.cs.msu.su ([158.250.17.23]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 07 Dec 2005 17:43:38 +0100 Received: from ghost by zigzag.lvk.cs.msu.su with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 07 Dec 2005 17:43:38 +0100 To: gdb@sources.redhat.com From: Vladimir Prus Subject: Re: Filename with "./" in breakpoint command Date: Wed, 07 Dec 2005 16:46:00 -0000 Message-ID: References: <200512050953.01350.ghost@cs.msu.su> <20051205185556.GA9808@nevyn.them.org> <20051206045518.GA23837@nevyn.them.org> <20051206201719.GA9140@nevyn.them.org> <20051206210900.GA10747@nevyn.them.org> <20051207145104.GA27164@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit User-Agent: KNode/0.8.2 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/msg00078.txt.bz2 Daniel Jacobowitz wrote: > On Wed, Dec 07, 2005 at 10:46:54AM +0300, Vladimir Prus wrote: >> > 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. >> >> Yes. I've just suggested that not supporting relative paths can be not >> very convenient for those directly using console interface. Especially >> when you say "break ./tracepoint.cpp:NNN", gdb suggests that this file >> might be in shared library that's no loaded yet, which can confuse users >> even more. >> >> I think either: >> >> 1. Relative paths should be handled fine, or >> 2. Relative paths should produce a warning from gdb. > > I'd rather #1. But, there's a lot of room for what "fine" is. > Relative only to $cdir? Relative to the directory search path? I'd say relatively to $cdir. I just did not though about the second approach, and I still think $cdir is more intuitive. - Volodya