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

[Nick Roberts <nickrob@snap.net.nz>]

 > > 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.

It would change the behviour of those commands but I guess it could be added
as an option.  I started looking at the frame ID to detect when the stack
changed in:

http://sourceware.org/ml/gdb/2006-06/msg00162.html

but Daniel J said:

  DJ> You can encounter the same frame ID for two consecutive stops
  DJ> but have a different backtrace, e.g. if you continued and then
  DJ> hit a breakpoint near the same function.

More recently I looked at Apple's approach which seems to just add a hook
in select_frame:

http://sourceware.org/ml/gdb-patches/2007-01/msg00037.html

-- 
Nick                                           http://www.inet.net.nz/~nickrob