From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28495 invoked by alias); 21 Mar 2002 11:44:15 -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 28455 invoked from network); 21 Mar 2002 11:44:13 -0000 Received: from unknown (HELO dublin.ACT-Europe.FR) (212.157.227.154) by sources.redhat.com with SMTP; 21 Mar 2002 11:44:13 -0000 Received: from berlin.ACT-Europe.FR (berlin.int.act-europe.fr [10.10.0.169]) by dublin.ACT-Europe.FR (Postfix) with ESMTP id 0C8A422A005; Thu, 21 Mar 2002 12:44:12 +0100 (MET) Received: by berlin.ACT-Europe.FR (Postfix, from userid 507) id 64F0D963; Thu, 21 Mar 2002 12:44:11 +0100 (CET) Date: Thu, 21 Mar 2002 03:44:00 -0000 From: Joel Brobecker To: Tom Tromey Cc: gdb-patches@sources.redhat.com Subject: Re: [RFC] gdb_realpath causes problems with GVD Message-ID: <20020321124411.A3351@act-europe.fr> References: <20020319171236.D6465@act-europe.fr> <87adt2ri93.fsf@creche.redhat.com> <20020321091144.A30346@act-europe.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020321091144.A30346@act-europe.fr>; from brobecker@ACT-Europe.FR on Thu, Mar 21, 2002 at 09:11:45AM +0100 X-SW-Source: 2002-03/txt/msg00407.txt.bz2 > It would be useful if you could find such a counter example, because it > would help me for future work in GDB to undertand if there was something > I missed. I think a counter example would definitely be helpful. > Supposing that this problem can be corrected entirely in GVD, should I > withdraw my change request? I would still prefer GDB to display toto.c > rather than toto.C as the basename part, but I don't have a strong > opinion so the advice of all GDB developers would be welcome. Based on a discussion I had with the GVD developers, I think that there is still some work needed to be done in GDB. When you start GVD on a program, GVD does an "info sources" to get the list of files, and then presents this list in a tree on which the user can click to view the file, put breakpoints, etc. The list looks like this: << toto.c, ../wcsmbs/wchar.h, ../iconv/gconv.h, ../include/gconv.h, ../sysdeps/unix/sysv/linux/i386/bits/wchar.h, >> As you see, there is no path information regarding toto.c. In my relatively modest experience, I find that the most common case of compiler invocation is "compiler /" This is means that most of the time, info sources will print a list of filenames with either relative path or no path at all. In order to locate a file, GVD needs to ask GDB. This is what it does using the "info line toto.c:1" command. To which GDB answers "/toto.C". But then, GDB refuses to put a breakpoint on toto.C unless one uses the full path. GDB is inconsistent here, and I really believe this inconsistency needs to be fixed. Either we modify GDB to be able to accept breakpoints on toto.C, or we make sure toto.c is not translated into toto.C. I think the shortest route is to avoid the toto.c -> toto.C translation. Comments? -- Joel