This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


> 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?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]