MI: performance of getting stack arguments

[Robert Dewar]

Jim Ingham wrote:
> Do you really have a UI that shows the stack arguments for ALL the 
> frames on the stack?  That's very unusual (and visually a bit 
> overwhelming, I would imagine).  The usual stack display shows the stack 
> with just the function names.  Then clicking on any given stack will 
> populate the arguments for that frame, fill the source window with the 
> source for that frame, etc...  This way, you only need to fetch the 
> arguments for the bottom-most frame on the stack when you stop 
> stepping.  You would only fetch the other stack arguments if the user 
> specifically requests them.

The ordinary bt from gdb gives this info, and it would be a pain
not to have it!