From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16585 invoked by alias); 19 Jul 2011 09:57:20 -0000 Received: (qmail 16577 invoked by uid 22791); 19 Jul 2011 09:57:19 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from fencepost.gnu.org (HELO fencepost.gnu.org) (140.186.70.10) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 19 Jul 2011 09:56:47 +0000 Received: from eliz by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1Qj72j-0002Fw-J4; Tue, 19 Jul 2011 05:56:45 -0400 Date: Tue, 19 Jul 2011 10:48:00 -0000 Message-Id: From: Eli Zaretskii To: Daniel Jacobowitz CC: jan.kratochvil@redhat.com, gdb-patches@sourceware.org In-reply-to: (message from Daniel Jacobowitz on Mon, 18 Jul 2011 17:01:44 -0400) Subject: Re: [RFC 06/12] entryval: Display @entry parameters in bt full Reply-to: Eli Zaretskii References: <20110718201852.GG30496@host1.jankratochvil.net> 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-07/txt/msg00453.txt.bz2 > Date: Mon, 18 Jul 2011 17:01:44 -0400 > From: Daniel Jacobowitz > Cc: gdb-patches@sourceware.org > > I am not in love with the @entry name, but maybe we can combine it > with the above... something like "$at_entry(p)" that could be > evaluated in an expression? Better naming welcome. Maybe I'm missing something important here (in fact, most probably I am), but let me turn the table and ask: why do we need that @entry qualifier at all? Why not just show the name of the parameter itself in the backtrace and let users evaluate `p' in expressions to mean that value which GDB can recover under this series of patches?