From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26115 invoked by alias); 20 Mar 2002 12:05:51 -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 24539 invoked from network); 20 Mar 2002 12:03:35 -0000 Received: from unknown (HELO dublin.ACT-Europe.FR) (212.157.227.154) by sources.redhat.com with SMTP; 20 Mar 2002 12:03:35 -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 D2DF0229FFF; Wed, 20 Mar 2002 13:03:34 +0100 (MET) Received: by berlin.ACT-Europe.FR (Postfix, from userid 507) id D7CA396B; Wed, 20 Mar 2002 13:03:30 +0100 (CET) Date: Wed, 20 Mar 2002 04:05:00 -0000 From: Joel Brobecker To: Eli Zaretskii Cc: drow@mvista.com, gdb-patches@sources.redhat.com Subject: Re: [RFC] gdb_realpath causes problems with GVD Message-ID: <20020320130330.E22439@act-europe.fr> References: <20020320101408.C22439@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: ; from eliz@is.elta.co.il on Wed, Mar 20, 2002 at 01:10:54PM +0200 X-SW-Source: 2002-03/txt/msg00384.txt.bz2 > What version of GDB was that, and what debug info format does your > compiler use? It was with GNU gdb 2002-03-19-cvs, and I used stabs. I verified in the assembly file that the path is stored in the debug information, and that objdump --debugging gives me the path as well. > This certainly works for me, at least in GDB 5.1.1 with stabs and DWARF2 > debug info. It doesn't work with COFF debug info, but that's because > COFF doesn't record the leading directories, only the basename. I tried it with several combinations of GCC, GDB, and debug format, and did not get it to work until I changed the compilation command to provide the fullpath of the file I was compiling: gcc -g -o toto /toto.c In this case, completion works, and I verified that my change does not break completion. As an aside after all my experiments, it seems that the break command is only using the information corresponding to the DW_AT_name entry (in stabs, this is the second N_SO entry)... Is there anything else that I missed regarding this file-completion issue? -- Joel