From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1289 invoked by alias); 18 Mar 2003 10:31:35 -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 1153 invoked from network); 18 Mar 2003 10:31:32 -0000 Received: from unknown (HELO nick.uklinux.net) (194.247.49.113) by sources.redhat.com with SMTP; 18 Mar 2003 10:31:32 -0000 Received: by nick.uklinux.net (Postfix, from userid 501) id 6FEF076037; Tue, 18 Mar 2003 10:27:38 +0000 (GMT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15990.62618.114706.459904@nick.uklinux.net> Date: Tue, 18 Mar 2003 10:31:00 -0000 To: Andrew Cagney Cc: gdb-patches@sources.redhat.com, bob_rossi@cox.net Subject: Re: [rfc] Annotation level THREE In-Reply-To: <3E763228.9060104@redhat.com> References: <3E6E7326.3020906@redhat.com> <15985.7336.23998.590592@nick.uklinux.net> <3E751565.4030409@redhat.com> <15990.10811.61395.996906@nick.uklinux.net> <3E763228.9060104@redhat.com> X-SW-Source: 2003-03/txt/msg00393.txt.bz2 > > > Why do you need display-{begin,end}? -display-insert has been made > > > redundant by the varobj stuff - it lets the GUI efficiently track its > > > display values outside of the CLI. > > > > Variable objects don't auto-display. You seem to have to type > > -var-evaluate-expression each time the program stops. > > Why do you need auto-display? What are you using it for? > > Remember, every time the target changes (e.g., from a user modifying a > variable or register), the display needs to be updated. This is because > that variable/register has the potential to modify every single value > being displayed. Further, unless your using some sort of changes-only > mechanism, such as provided by the varobj, the display windows are just > not going to scale. You're right. If the user assigns a value to a variable, using my code, the display window for that variable won't update in Emacs until the next statement is executed. What do you mean by `not going to scale'? Currently if I display an array slice, say just a few elements from a large array, I need to parse them from output for the whole array. Could I arrange for GDB to just output the elements I want using variable objects? Can I get GDB to tell me what the current list of variable objects is? Can I generate names for them automatically? > > > The testsuite is a good source of > > > varobj examples (unfortunatly lacking from the doco): > > > http://sources.redhat.com/gdb/current/onlinedocs/gdb_25.html#SEC565 > > > > The lack of documentation for (and apparent completeness of) GDB/MI is part of > > the problem. > > Um, the varobj is documented. It just lacks a vew concrete examples. > Those can be found by examining the testsuite. Both Apple and Eclipse > are using this part of the MI. Its a question of resources. I'm one person doing things in my spare time. Apple and Eclipse have full time teams dedicated to the task. > > > The above list also contains thing like field-{begin,end}, > > > array-section-{begin,end} et.al. Why are they needed. > > > > I use them to parse the output. They could probably go, if necessary, but > > others that you plan to take out *are* needed. > > Can you please be more specific? Perhaps I could turn that question round. Which annotations are you planning to keep? Nick