From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5146 invoked by alias); 6 Dec 2011 12:50:07 -0000 Received: (qmail 5137 invoked by uid 22791); 6 Dec 2011 12:50:05 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 06 Dec 2011 12:49:53 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=EU1-MAIL.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1RXuT0-0000xt-WC from pedro_alves@mentor.com ; Tue, 06 Dec 2011 04:49:51 -0800 Received: from scottsdale.localnet ([172.16.63.104]) by EU1-MAIL.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 6 Dec 2011 12:49:49 +0000 From: Pedro Alves To: Eli Zaretskii Subject: Re: [patch] GDB 7.2: new feature for "backtrace" that cuts path to file (remain filename) Date: Tue, 06 Dec 2011 13:03:00 -0000 User-Agent: KMail/1.13.6 (Linux/2.6.38-13-generic; KDE/4.7.2; x86_64; ; ) Cc: hal9000ed2k@gmail.com, tromey@redhat.com, dje@google.com, gdb-patches@sourceware.org, pmuldoon@redhat.com, brobecker@adacore.com, drow@false.org, jan.kratochvil@redhat.com References: <83fwgzbrp9.fsf@gnu.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201112061249.47758.pedro@codesourcery.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-12/txt/msg00167.txt.bz2 On Monday 05 December 2011 05:17:19, Eli Zaretskii wrote: > > Date: Mon, 05 Dec 2011 05:52:34 +0200 > > From: Eli Zaretskii > > And what about the question I asked regarding the default? AFAIK, the > > current behavior is equivalent to `basename', not to `full'. > > I think I know the answer. We show by default whatever the compiler > saw on its command line when it compiled the source file. E.g., if > the command was > > gcc -c ... /foo/bar/baz.c > > then GDB will show "/foo/bar/baz.c", but if the compilation command > was > > gcc -c ... baz.c > > then GDB will show "baz.c". > > Is that correct? If so, calling this `full' is misleading, I think, If that is correct, than the default isn't "full", but the proposed "no-compile-directory" ? Or maybe your compiler didn't emit the comp_dir attribute in the debug info. I don't really know what is the current default, and I'm now confused too. :-) > unless we really change GDB to always show a full absolute file name > there. If we don't want to change, I suggest to call it `normal' or > maybe `default' (with explanation along the above lines). I don't think normal or default are good names (with IMO default being a really bad name), because that'll confuse things a lot if we ever flip the default. -- Pedro Alves