From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3744 invoked by alias); 27 Nov 2006 00:43:34 -0000 Received: (qmail 3736 invoked by uid 22791); 27 Nov 2006 00:43:33 -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; Mon, 27 Nov 2006 00:43:27 +0000 Received: from kahikatea.snap.net.nz (p202-124-125-70.snap.net.nz [202.124.125.70]) by viper.snap.net.nz (Postfix) with ESMTP id 7AB103DAED6; Mon, 27 Nov 2006 13:44:06 +1300 (NZDT) Received: by kahikatea.snap.net.nz (Postfix, from userid 500) id 7D9FABE44C; Mon, 27 Nov 2006 13:39:10 +1300 (NZDT) From: Nick Roberts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17770.13228.627008.188019@kahikatea.snap.net.nz> Date: Mon, 27 Nov 2006 00:43: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.3 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-11/txt/msg00292.txt.bz2 > At the moment, MI varobj assume that register values have a language. As > result, if you try to look at values of $xmm1 in a C++ program, you'll find > that this registers has a 'public' field -- which is not reasonable. > The attached patch causes MI to always force the C language for register > values, so no special processing takes place. OK? Experimenting with register names as variable objects: With C: -var-create - * $xmm1 ^done,name="var1",numchild="7",type="builtin_type_vec128i" (gdb) -var-list-children var1 &"Attempt to take address of value not located in memory.\n" ^error,msg="Attempt to take address of value not located in memory." With C++ -var-create - * $xmm1 ^done,name="var1",numchild="1",type="builtin_type_vec128i" (gdb) -var-list-children var1 Segmentation fault (core dumped) but there are already MI commands for registers. Notably -data-list-register-values and -data-list-changed-registers which is a bit like var-update. What advantage do variable objects offer for register names? -- Nick http://www.inet.net.nz/~nickrob