From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6125 invoked by alias); 6 Dec 2006 21:54:40 -0000 Received: (qmail 6032 invoked by uid 22791); 6 Dec 2006 21:54:38 -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; Wed, 06 Dec 2006 21:54:27 +0000 Received: from kahikatea.snap.net.nz (p202-124-120-99.snap.net.nz [202.124.120.99]) by viper.snap.net.nz (Postfix) with ESMTP id 4B0BC3DA830; Thu, 7 Dec 2006 10:55:26 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 500) id B5D60BE3D4; Thu, 7 Dec 2006 10:49:59 +1300 (NZDT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17783.15109.940151.497949@kahikatea.snap.net.nz> Date: Wed, 06 Dec 2006 21:54:00 -0000 To: Vladimir Prus Cc: gdb-patches@sources.redhat.com Subject: Re: Language of registers X-Mailer: VM 7.19 under Emacs 22.0.91.13 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: 2006-12/txt/msg00079.txt.bz2 > > What advantage do variable objects offer for register names? > To begin with -- consistenly. There is no fundamental difference between > ordinary values and registers. Is that true? Is the logic not simpler for registers? No need to use GDB's notion of values, check whether they've been fetched etc. > The frontend knows how to display the > hierarchy of variable objects, and there's no need to force the frontend to > have additional logic for register. Note that Eclipse, for example, does > create variable objects for all registers at the moment. What hierarchy are you talking about? Would a variable object for a register have children? > The second advantage is that -data-list-register-values has no hierarchy at > all. If you try > -data-list-register-values xmm1 > then gdb print print half-screen of output that should be specially parsed > and displayed. I think that's because your syntax is wrong: -data-list-register-names 33 ^done,register-names=["xmm1"] (gdb) -data-list-register-values x 33 ^done,register-values=[{number="33",value="{v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {0x0 }, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000}"}] > When using variable objects, the frontend already has the > parsing/display code. What would your variable object print for xmm1? -- Nick http://www.inet.net.nz/~nickrob