From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31340 invoked by alias); 6 Dec 2011 17:33:04 -0000 Received: (qmail 31309 invoked by uid 22791); 6 Dec 2011 17:33:02 -0000 X-SWARE-Spam-Status: No, hits=-3.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail-vw0-f41.google.com (HELO mail-vw0-f41.google.com) (209.85.212.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 06 Dec 2011 17:32:49 +0000 Received: by vbbfn1 with SMTP id fn1so2892011vbb.0 for ; Tue, 06 Dec 2011 09:32:48 -0800 (PST) Received: by 10.52.20.35 with SMTP id k3mr9123508vde.34.1323192768775; Tue, 06 Dec 2011 09:32:48 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.20.35 with SMTP id k3mr9123480vde.34.1323192768604; Tue, 06 Dec 2011 09:32:48 -0800 (PST) Received: by 10.220.97.211 with HTTP; Tue, 6 Dec 2011 09:32:48 -0800 (PST) In-Reply-To: References: <83fwgzbrp9.fsf@gnu.org> <201112061249.47758.pedro@codesourcery.com> Date: Tue, 06 Dec 2011 18:00:00 -0000 Message-ID: Subject: Re: [patch] GDB 7.2: new feature for "backtrace" that cuts path to file (remain filename) From: Doug Evans To: Eli Zaretskii Cc: Pedro Alves , hal9000ed2k@gmail.com, tromey@redhat.com, gdb-patches@sourceware.org, pmuldoon@redhat.com, brobecker@adacore.com, drow@false.org, jan.kratochvil@redhat.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true 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/msg00183.txt.bz2 On Tue, Dec 6, 2011 at 5:03 AM, Eli Zaretskii wrote: >> From: Pedro Alves >> Date: Tue, 6 Dec 2011 12:49:47 +0000 >> Cc: hal9000ed2k@gmail.com, >> =A0tromey@redhat.com, >> =A0dje@google.com, >> =A0gdb-patches@sourceware.org, >> =A0pmuldoon@redhat.com, >> =A0brobecker@adacore.com, >> =A0drow@false.org, >> =A0jan.kratochvil@redhat.com >> >> > if the command was >> > >> > =A0 gcc -c ... /foo/bar/baz.c >> > >> > then GDB will show "/foo/bar/baz.c", but if the compilation command >> > was >> > >> > =A0 gcc -c ... baz.c >> > >> > then GDB will show "baz.c". >> >> > >> > Is that correct? =A0If so, calling this `full' is misleading, I think, >> >> If that is correct, than the default isn't "full", but >> the proposed "no-compile-directory" ? > > No, it's `full', because the compile directory was "/foo/bar". > >> Or maybe your compiler didn't emit the comp_dir attribute in the >> debug info. > > "My compiler" in this case identifies itself as > > =A0gcc (Ubuntu 4.4.3-4ubuntu5) 4.4.3 > > I'd be surprised if this version omits comp_dir, but if someone tells > me how to check that, I will. > >> I don't really know what is the current default, and I'm now >> confused too. =A0:-) > > Then I'm in good company ;-) > >> > unless we really change GDB to always show a full absolute file name >> > there. =A0If 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 > > Then maybe "as-recorded"? =A0Meaning that this is how the compiler > recorded the file name in the debug info? I like that. Something along the lines of "set backtrace file-name as-recorded|full|base= " ?