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

[Jan Kratochvil <jan.kratochvil@redhat.com>]

On Tue, 19 Jul 2011 11:56:45 +0200, Eli Zaretskii wrote:
> Maybe I'm missing something important here (in fact, most probably I am), 

Yes.

> but let me turn the table and ask: why do we need that @entry
> qualifier at all?

The patchset would be useful for recovering the lost values without showing or
entering the @entry string anywhere, that is without having the entry values
explicitly user accessible 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?

Yes, it works that way.


GDB internally knows the value of the parameter at the function entry - to be
able to recover the values.  It has been found out the developers may find it
useful to be shown the entry values it.  It is an additional feature on top of
the values recovery.

I think it is separated well enough in the patchset, up to incl. 05/12 it is
about values recovery, from 06/12 it is about user-accessible entry values.


Thanks,
Jan