From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-85791-listarch-gdb-patches=sources.redhat.com@sourceware.org>
Received: (qmail 27157 invoked by alias); 5 Dec 2011 03:54:25 -0000
Received: (qmail 27145 invoked by uid 22791); 5 Dec 2011 03:54:24 -0000
X-SWARE-Spam-Status: No, hits=-0.9 required=5.0	tests=AWL,BAYES_00,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Received: from mtaout20.012.net.il (HELO mtaout20.012.net.il) (80.179.55.166)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 05 Dec 2011 03:54:08 +0000
Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0LVP00L00P4U9I00@a-mtaout20.012.net.il> for gdb-patches@sourceware.org; Mon, 05 Dec 2011 05:53:38 +0200 (IST)
Received: from HOME-C4E4A596F7 ([77.126.238.56]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LVP00KH5PHCRD70@a-mtaout20.012.net.il>; Mon, 05 Dec 2011 05:53:38 +0200 (IST)
Date: Mon, 05 Dec 2011 03:54:00 -0000
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [patch] GDB 7.2: new feature for "backtrace" that cuts path to file (remain filename)
In-reply-to: <201112042100.17292.pedro@codesourcery.com>
To: Pedro Alves <pedro@codesourcery.com>
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
Reply-to: Eli Zaretskii <eliz@gnu.org>
Message-id: <83fwgzbrp9.fsf@gnu.org>
References: <BANLkTinD+9_Mkug8o2VhZ03L6XSriL_RKQ@mail.gmail.com> <201112041901.04599.pedro@codesourcery.com> <83hb1gaz88.fsf@gnu.org> <201112042100.17292.pedro@codesourcery.com>
X-IsSubscribed: yes
Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-patches.sourceware.org>
List-Subscribe: <mailto:gdb-patches-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sourceware.org>
List-Help: <mailto:gdb-patches-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-patches-owner@sourceware.org
X-SW-Source: 2011-12/txt/msg00110.txt.bz2

> From: Pedro Alves <pedro@codesourcery.com>
> Date: Sun, 4 Dec 2011 21:00:16 +0000
> 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
> 
> $ 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.

How about `relative-to-compilation-directory'?  Or just `relative'
(since we use `full', not `full-absolute-file-name')?

And what about the question I asked regarding the default?  AFAIK, the
current behavior is equivalent to `basename', not to `full'.

Thanks.