From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28463 invoked by alias); 27 Aug 2002 21:20:27 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 28449 invoked from network); 27 Aug 2002 21:20:26 -0000 Received: from unknown (HELO valrhona.uglyboxes.com) (64.1.192.220) by sources.redhat.com with SMTP; 27 Aug 2002 21:20:26 -0000 Received: from localhost.localdomain (IDENT:ttrv3jgoM4SWSJcQcQxwrQW2sSDI+k+7@localhost.localdomain [127.0.0.1]) by valrhona.uglyboxes.com (8.11.6/8.11.6) with ESMTP id g7RLN8v23727 for ; Tue, 27 Aug 2002 14:23:08 -0700 Date: Tue, 27 Aug 2002 14:40:00 -0000 From: Keith Seitz X-X-Sender: keiths@valrhona.uglyboxes.com To: gdb-patches@sources.redhat.com Subject: Re: [RFA] add selected-frame-level-changed events In-Reply-To: <3D6BEB28.8050207@ges.redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-08/txt/msg00913.txt.bz2 On Tue, 27 Aug 2002, Andrew Cagney wrote: > Why not put it in there anyway? You mean add a notification in select_frame? Because UIs don't care when GDB is temporarily switching frames for whatever reason. What matters is when something happens to cause the current frame to be changed and cause gdb and the MI client to get out of sync. As far as I know, this only happens via the command line frame commands (up, down, frame). There might be others, but I've never seen them. > I think, not putting it in select_frame() is the part that needs the fixme. Right, that's what I meant. Sorry if I was vague. Ideally, we would like it in select_frame, but we cannot do that right now because the UI would be informed of billions of frame changes per step, especially if varobj is operating. Keith