From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6657 invoked by alias); 16 Jan 2007 22:52:29 -0000 Received: (qmail 6648 invoked by uid 22791); 16 Jan 2007 22:52:28 -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; Tue, 16 Jan 2007 22:52:20 +0000 Received: from kahikatea.snap.net.nz (unknown [123.255.62.204]) by viper.snap.net.nz (Postfix) with ESMTP id 00C4A3D8275; Wed, 17 Jan 2007 11:52:12 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 500) id 196394F711; Wed, 17 Jan 2007 11:52:09 +1300 (NZDT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17837.22296.701551.796666@kahikatea.snap.net.nz> Date: Tue, 16 Jan 2007 22:52:00 -0000 To: Vladimir Prus Cc: Daniel Jacobowitz , gdb@sources.redhat.com Subject: Re: -var-list --locals proposal In-Reply-To: <200701161920.17596.ghost@cs.msu.su> References: <200701052303.59465.ghost@cs.msu.su> <20070116071845.GA16388@nevyn.them.org> <200701161920.17596.ghost@cs.msu.su> X-Mailer: VM 7.19 under Emacs 22.0.92.10 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: 2007-01/txt/msg00263.txt.bz2 > So, you either have frame_id->list_of_varobjs mapping in gdb, or in > the frontend. I'm not sure which one is better. If this kept in a frontend, > you'd also need notification "frame id XXX has died" so that > the frontend can clean up its mapping. I think there should varobjs that are created from locals which get deleted when leaving the frame, and ordinary varobjs (which I guess could get deleted if they aren't globals). Normally the user won't create two watch expressions for the same variable but I think that should be his business. I think it would be hard to avoid duplication as one watch expression might be a child object. > We'd need similar thing for function arguments, perhaps -- command like > > -var-list --arguments In Insight arguments are listed alongside locals. It might be a good idea to have: -var-list --args-and-locals and perhaps a field to say which is which. It seems sensible to list them all in one window. > that would try hard to reuse varobjs and which command can be used > to implement stack display. I'd much prefer to have this logic in gdb, > because doing it in the frontend is not anyway simpler, I think. -- Nick http://www.inet.net.nz/~nickrob