Re: [RFA] Have block_innermost_frame start from selected frame

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

On Wed, 28 Dec 2011 16:30:08 +0100, Joel Brobecker wrote:
> What do you mean by ambiguous? Is it the case described here, where
> we have multiple frames for the given FUNCTION?

Yes.  Depending on which recursive function frame you select the returned
value is different.


> I don't think we should query().

In fact we should menu-select them but that is offtopic now.


> Users often respond negatively to query, particularly in a case like this
> where we can make the behavior unambiguous and easily describable.

I find that GDB should ask or at least warn more in general.  Like that if you
debug -O2 code it should warn you on first `step' that it will not work much.
If you debug program/function without -g it should warn you (not just "no
debugging symbols found" lost in the screens of "Reading symbols from "
messages).  It would prevent false accuses of GDB due to bugs elsewhere.

GIT gives nice messages suggesting what to do in any case of a problem.


> It's the only way to get the value of "var" in our testcase, and you cannot
> currently do it with the old behavior.

You can already do so many things with GDB, just people do not do even 5% of
them because it is all too magic to learn.


> I think simple is good enough, in this particular case.

I am not going to try to block it but it is still the current GDB style closed
to hackers.


Thanks,
Jan