Re: [PATCH] -stack-select-frame

[Bob Rossi <bob@brasko.net>]

On Fri, Jun 17, 2005 at 10:50:30AM +1200, Nick Roberts wrote:
>  > My concern was that this added a new item to a response which previous
>  > had zero.  Why do you think people couldn't use it as is?  Seems
>  > perfectly usable to me; if you know the level of a frame you want to
>  > select, then you probably already have the result of a backtrace which
>  > includes a printout of the stack frame, so you probably don't need
>  > another!
> 
> -stack-select-frame without an argument currently works like the CLI command
> "frame" without the output.  All "frame" does is output the current frame,
> so without output its a bit of a no-op.
> 
> -stack-select-frame with an argument just works like up, down or more
> precisely "frame FRAMENUM".  So ,these CLI commands could be used directly in
> the short term, and via "-interpreter-exec console" in the longer term, if the
> frontend is not interested in the output.
> 
>  > Could you explain why you think we need output here?
> 
> If you have a backtrace then, no, you don't need the output and the frontend
> can ignore it.  However, I presume "-stack-select-frame" runs more quickly
> than "-stack-list-frames" so, if you don't need a backtrace, its probably best
> not to require one.

Yes, that sounds nice. Especially on an infinate recursion crash. The
stack trace would take way to long to get back, so going frame by frame
would be much nicer.

Bob Rossi