From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10346 invoked by alias); 4 Dec 2011 21:00:37 -0000 Received: (qmail 10337 invoked by uid 22791); 4 Dec 2011 21:00:37 -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; Sun, 04 Dec 2011 21:00:23 +0000 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=EU1-MAIL.mgc.mentorg.com) by relay1.mentorg.com with esmtp id 1RXJAa-0006JL-US from pedro_alves@mentor.com ; Sun, 04 Dec 2011 13:00:21 -0800 Received: from scottsdale.localnet ([172.16.63.104]) by EU1-MAIL.mgc.mentorg.com with Microsoft SMTPSVC(6.0.3790.1830); Sun, 4 Dec 2011 21:00:19 +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: Sun, 04 Dec 2011 21:00: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: <201112041901.04599.pedro@codesourcery.com> <83hb1gaz88.fsf@gnu.org> In-Reply-To: <83hb1gaz88.fsf@gnu.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201112042100.17292.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/msg00108.txt.bz2 On Sunday 04 December 2011 19:55:19, Eli Zaretskii wrote: > > From: Pedro Alves > > On Sunday 04 December 2011 18:41:16, iam ahal wrote: > > > > of without-compilation-directory. > > > > At the risk of being bikesheddy, I suggest "no-compilation-directory" instead. > > 5 whole letters less. :-) Somehow it sounds more gdb-idiomatic to me. > > Fine with me, but it still falls short of explaining what exactly is > removed from the file name. The working directory of the compilation command that produced the frame's compilation unit. E.g., with: $ pwd /foo/bar $ gcc a/b.c If the debug info supports a notion of compilation directory (DW_AT_comp_dir in dwarf), the full name is /foo/bar/a/b.c and the compilation directory is /foo/bar. The no-compilation-directory option would the show a/b.c . I'd rather have a positive option, rather than a negative one (no-|without-), but I'm failing to find a better name. I thought of "relative", but that's not entirely accurate -- it can be a full path too. I can live with no-compilation-directory. Just saying I tried and failed. -- Pedro Alves