From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15602 invoked by alias); 23 Feb 2009 16:05:32 -0000 Received: (qmail 15581 invoked by uid 22791); 23 Feb 2009 16:05:29 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_37,RCVD_IN_DNSWL_LOW,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from main.gmane.org (HELO ciao.gmane.org) (80.91.229.2) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 23 Feb 2009 16:05:20 +0000 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LbdIx-0002KF-Lx for gdb-patches@sources.redhat.com; Mon, 23 Feb 2009 16:05:15 +0000 Received: from enigma.qnx.com ([209.226.137.106]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 23 Feb 2009 16:05:15 +0000 Received: from aristovski by enigma.qnx.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 23 Feb 2009 16:05:15 +0000 To: gdb-patches@sources.redhat.com From: Aleksandar Ristovski Subject: Re: [patch] mips-tdep: info registers Date: Mon, 23 Feb 2009 16:18:00 -0000 Message-ID: References: <20090223020820.GC26056@adacore.com> <20090223025230.GA11699@caradoc.them.org> <20090223030014.GE26056@adacore.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------070400010309080100040909" User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) In-Reply-To: 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: 2009-02/txt/msg00442.txt.bz2 This is a multi-part message in MIME format. --------------070400010309080100040909 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-length: 1429 Eli Zaretskii wrote: >> Date: Sun, 22 Feb 2009 19:00:14 -0800 >> From: Joel Brobecker >> >>>> Surprisingly, this feature is not documented yet. The documentation >>>> mentions "info registers regname", but not "info registers regno". >>>> Would you mind adding a line or two and sending a (separate) patch >>>> to this list? Eli is the documentation guru... >>> Should this feature even exist? This is a different "$1" than >>> anywhere else in GDB you might type that... >> I was asking myself this question, but there is explict code in >> GDB to handle that case, so I thought that this was deliberate. >> On the other hand, I also thought that this was a very cool way >> of knowing what register number NUM actually is. For instance, >> on x86, register number 3 is (drums...) ebx: >> >> (gdb) info reg $3 >> ebx 0xb7e84ff4 -1209511948 >> >> With x86, the number of registers is fairly limited, but there >> are other processors where this isn't the case. The CPU that gave >> me the largest number of pimples so far is ia64... >> >> So I found that the above syntax was a cool thing to know about >> and worth retaining. > > I agree. Documenting it would be good, thanks. > I added a note about the regno syntax. Thanks, Aleksandar Ristovski QNX Software Systems ChangeLog: * gdb.texinfo (info registers): Add a note about permitted info registers regno syntax. --------------070400010309080100040909 Content-Type: text/x-patch; name="mips-tdep.c-info-registers-doc-20090223.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="mips-tdep.c-info-registers-doc-20090223.diff" Content-length: 523 Index: gdb/doc/gdb.texinfo =================================================================== RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v retrieving revision 1.558 diff -r1.558 gdb.texinfo 7436a7437,7442 > > Note that syntax using register number (@var{regno}) in place of > @var{regname} is also permitted. While for some architectures (like x86) > @var{regno} has a meaning only within @value{GDBN} context and is > subject to change in different @value{GDBN} versions, others (like mips) > explicitly define them. --------------070400010309080100040909--