Re: [PATCH] -stack-select-frame

[Daniel Jacobowitz <drow@false.org>]

On Fri, Jun 17, 2005 at 07:24:01PM +1200, Nick Roberts wrote:
>  > (one of the parts of this profiling which is especially useful is  
>  > that we have a "mi-timings-enabled" setting.  When it's enabled,  
>  > every MI command reports how long gdb took to complete it, e.g. the  
>  > "time=" bit at the end here:
>  > 
>  > -> 50-stack-list-frames 0 5
>  > <- 50^done,stack=[frame= 
>  > {level="0",addr="0x0009e7fc",fp="0xbfffe700",func=" [...] ,frame= 
>  > {level="5",addr="0x936265d0",fp="0xbfffeee0",func="-[NSApplication  
>  > run]"}],time= 
>  > {wallclock="0.14353",user="0.00584",system="0.00335",start="1118952348.0 
>  > 03847",end="1118952348.147372"}
> 
> Yes but what happens when the stack is much deeper, 20 or 30 say, like it can
> be when you you are debugging Emacs, or GDB for that matter?

Just a guess but: why ask GDB for more stack frames than fit in the
relevant window?  You can ask for more (to ensure smooth scrolling),
but do it while the user's doing something else.  An MI frontend
doesn't need to ask for all frames if it's worried about how long that
will take.

-- 
Daniel Jacobowitz
CodeSourcery, LLC