Re: [RFC 06/12] entryval: Display @entry parameters in bt full

Eli Zaretskii
2011-07-19T09:57:20Z

> Date: Mon, 18 Jul 2011 17:01:44 -0400
> From: Daniel Jacobowitz <drow@false.org>
> 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?