Re: [RFC] Prints the frame id when target stops

[Vladimir Prus <ghost at cs dot msu dot su>]

Denis PILAT wrote:

> We are optimizing the usage of MI commands into our Eclipse based UI.
> In some cases, it could take a while (and sometime more!) to refresh the
> thread list and the stack frame, and Eclipse does it very often.
> 
> We'd like to avoid refreshing the thread and the frame view when the
> user perform a step (or a next) and when the program stops in the same
> thread and in the same frame.
> In the stop reason we got the current thread id, but we are missing
> something to identify the frame.
> That patch lets gdb emits on the MI output a string that could be used
> to easily identify the current frame.
> If you are ok with this approach then I'll update the testsuite.

Would not a better approach be to modify -stack-list-frames and friends,
so that they check frame id internally, and it has not changed, just
return the same result? Such approach will uniformly help all frontends,
and won't expose new concepts in the interface.

- Volodya