From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14652 invoked by alias); 17 Jan 2007 21:29:22 -0000 Received: (qmail 14621 invoked by uid 22791); 17 Jan 2007 21:29:20 -0000 X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO brahms.sibelius.xs4all.nl) (82.92.89.47) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 17 Jan 2007 21:29:15 +0000 Received: from brahms.sibelius.xs4all.nl (kettenis@localhost.sibelius.xs4all.nl [127.0.0.1]) by brahms.sibelius.xs4all.nl (8.13.8/8.13.8) with ESMTP id l0HLSOXZ027468; Wed, 17 Jan 2007 22:28:24 +0100 (CET) Received: (from kettenis@localhost) by brahms.sibelius.xs4all.nl (8.13.8/8.13.8/Submit) id l0HLSOTc024176; Wed, 17 Jan 2007 22:28:24 +0100 (CET) Date: Wed, 17 Jan 2007 21:29:00 -0000 Message-Id: <200701172128.l0HLSOTc024176@brahms.sibelius.xs4all.nl> From: Mark Kettenis To: ghost@cs.msu.su CC: nickrob@snap.net.nz, denis.pilat@st.com, gdb-patches@sources.redhat.com In-reply-to: <200701170234.34303.ghost@cs.msu.su> (message from Vladimir Prus on Wed, 17 Jan 2007 02:34:34 +0300) Subject: Re: [RFC] Prints the frame id when target stops References: <45AB9A7F.1090502@st.com> <17837.16328.46414.146270@kahikatea.snap.net.nz> <200701170234.34303.ghost@cs.msu.su> Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2007-01/txt/msg00387.txt.bz2 > From: Vladimir Prus > Date: Wed, 17 Jan 2007 02:34:34 +0300 > > On Wednesday 17 January 2007 00:12, Nick Roberts wrote: > > > > 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. > > It actually won't. If -stack-list-frames is changed to return cached > result when it's absolutely clear that the stack did not change, you > have no behaviour change, just better performance. Unforunately, making absolutely sure the stack did not change may not be possible. Mark