From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13145 invoked by alias); 27 Nov 2006 07:37:13 -0000 Received: (qmail 13137 invoked by uid 22791); 27 Nov 2006 07:37:13 -0000 X-Spam-Check-By: sourceware.org Received: from heller.inter.net.il (HELO heller.inter.net.il) (192.114.186.73) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 27 Nov 2006 07:37:08 +0000 Received: from HOME-C4E4A596F7 (IGLD-84-228-213-128.inter.net.il [84.228.213.128]) by heller.inter.net.il (MOS 3.7.3a-GA) with ESMTP id BCN73304 (AUTH halo1); Mon, 27 Nov 2006 09:31:35 +0200 (IST) Date: Mon, 27 Nov 2006 07:37:00 -0000 Message-Id: From: Eli Zaretskii To: Vladimir Prus CC: gdb-patches@sources.redhat.com In-reply-to: (message from Vladimir Prus on Mon, 27 Nov 2006 09:32:09 +0300) Subject: Re: Language of registers Reply-to: Eli Zaretskii References: <17770.13228.627008.188019@kahikatea.snap.net.nz> X-IsSubscribed: yes 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/msg00294.txt.bz2 > From: Vladimir Prus > Date: Mon, 27 Nov 2006 09:32:09 +0300 > > > > What advantage do variable objects offer for register names? > > To begin with -- consistenly. There is no fundamental difference between > ordinary values and registers. 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. > > 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. When using variable objects, the frontend already has the > parsing/display code. It would be nice to have these explanation in the manual... Thanks.