From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2978 invoked by alias); 10 Jun 2008 02:54:14 -0000 Received: (qmail 2970 invoked by uid 22791); 10 Jun 2008 02:54:14 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.25) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 10 Jun 2008 02:53:49 +0000 Received: from kahikatea.snap.net.nz (215.60.255.123.dynamic.snap.net.nz [123.255.60.215]) by viper.snap.net.nz (Postfix) with ESMTP id F0B763DA0F0; Tue, 10 Jun 2008 14:53:41 +1200 (NZST) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id 448718FC6D; Tue, 10 Jun 2008 14:53:28 +1200 (NZST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18509.60583.390202.377448@kahikatea.snap.net.nz> Date: Tue, 10 Jun 2008 04:25:00 -0000 To: Daniel Jacobowitz Cc: gdb-patches@sources.redhat.com Subject: Re: [PATCH:MI] Event notification In-Reply-To: <20080610022945.GA27459@caradoc.them.org> References: <18439.56134.456709.118980@kahikatea.snap.net.nz> <20080501185728.GE22218@caradoc.them.org> <18509.56150.132277.869905@kahikatea.snap.net.nz> <20080610022945.GA27459@caradoc.them.org> X-Mailer: VM 7.19 under Emacs 22.2.50.2 X-IsSubscribed: yes 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: 2008-06/txt/msg00188.txt.bz2 > > How about conditioning it so that it only fires when the target isn't > > running, e.g., with the up, down, frame, -stack-select-frame etc commands? > > It's not about when the target is running. Consider updating varobjs; > for every varobj with an associated frame, we will select the frame > and it will pass through select_frame. Perhaps the answer then is to put notification explicitly in each CLI and MI command (as I've proposed for thread_command and mi_cmd_thread_select). However, it's always possible to just issue -stack-info-frame after execution has stopped and maybe that's never expensive enough to justify such a brute force approach. -- Nick http://www.inet.net.nz/~nickrob