From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28319 invoked by alias); 28 Jun 2011 20:08:02 -0000 Received: (qmail 28303 invoked by uid 22791); 28 Jun 2011 20:08:01 -0000 X-SWARE-Spam-Status: No, hits=-6.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 28 Jun 2011 20:07:40 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p5SK7Rth007306 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 28 Jun 2011 16:07:27 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p5SK7RBi002433; Tue, 28 Jun 2011 16:07:27 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id p5SK7PrC027229; Tue, 28 Jun 2011 16:07:25 -0400 From: Tom Tromey To: Joel Brobecker Cc: Phil Muldoon , iam ahal , gdb-patches@sourceware.org Subject: Re: [patch] GDB 7.2: new feature for "backtrace" that cuts path to file (remain filename) References: <20110627160029.GF20676@adacore.com> Date: Tue, 28 Jun 2011 20:08:00 -0000 In-Reply-To: <20110627160029.GF20676@adacore.com> (Joel Brobecker's message of "Mon, 27 Jun 2011 09:00:29 -0700") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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-06/txt/msg00425.txt.bz2 >>>>> "Joel" == Joel Brobecker writes: >> You could use Python to write a custom backtrace to do this. But that >> is neither here or there to this patch. Joel> Yeah, I am wondering which way would be best. It seems like a Python Joel> backtrace decorator would already work, or could be made to work. We have a plan to implement "frame filters" in Python. The idea here is basically pretty-printing for backtraces -- let libraries ship Python code to modify frames while they are being displayed. E.g., the Python interpreter could replace C frames with synthetic frames representing the Python stack. Full details are available somewhere -- either archer or gdb list archives. If you want to read them and can't find them, let me know, and I will either dig them up or write them again. Phil would have to say the status of this work. Joel> So, there are pluses and minuses on both ends. I am wondering Joel> what everyone else thinks... I am happy adding any vaguely sensible setting that people want to the core. Why not? The time more minimalism has long passed. Whether this one meets the bar, I don't know. Is basename really the obvious transform to apply? What about just dropping the compilation directory? Joel> If we were to implement this in GDB itself, I'd rather go with Joel> a setting rather than a command-line option. But that's just Joel> a suggestion. Definitely a setting and not a command-line option. Tom