From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17372 invoked by alias); 20 Mar 2008 20:57:53 -0000 Received: (qmail 17361 invoked by uid 22791); 20 Mar 2008 20:57:52 -0000 X-Spam-Check-By: sourceware.org Received: from viper.snap.net.nz (HELO viper.snap.net.nz) (202.37.101.8) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 20 Mar 2008 20:57:21 +0000 Received: from kahikatea.snap.net.nz (222.31.255.123.static.snap.net.nz [123.255.31.222]) by viper.snap.net.nz (Postfix) with ESMTP id 579223DABC9; Fri, 21 Mar 2008 09:57:14 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id F2BD18FC6D; Fri, 21 Mar 2008 08:53:03 +1200 (NZST) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18402.52910.383094.665060@kahikatea.snap.net.nz> Date: Fri, 21 Mar 2008 09:11:00 -0000 To: "Marc Khouzam" Cc: "Vladimir Prus" , Subject: RE: MI non-stop mode spec In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA04290FB4@ecamlmw720.eamcs.ericsson.se> References: <200803190016.02072.vladimir@codesourcery.com> <6D19CA8D71C89C43A057926FE0D4ADAA04290FB4@ecamlmw720.eamcs.ericsson.se> X-Mailer: VM 7.19 under Emacs 22.1.92.2 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-03/txt/msg00187.txt.bz2 > > -> Should @ varobjs be bound to only thread, or to nothing at all. > > This is an interesting question. It brings the possibility of supporting > both those options. That would mean three types of variable objects: > 1- bound to a frame > 2- bound to a thread > 3- not bound I think there are more than three possibilities: 1) bound to the frame in which varobj is created (*). 2) bound to the selected frame (@) 3) bound to the thread in which varobj is created and 1) 4) bound to the thread in which varobj is created and 2) 5) bound to the selected thread and 1) 6) bound to the selected thread and 2) Maybe there are more, e.g, all threads (I've not really thought them through) Currently only 1) works and 2) has a broken implementation. -- Nick http://www.inet.net.nz/~nickrob