Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: aristovski@qnx.com, gdb-patches@sources.redhat.com
Subject: Re: [patch] mips-tdep: info registers
Date: Mon, 23 Feb 2009 08:53:00 -0000	[thread overview]
Message-ID: <u8wnxu77c.fsf@gnu.org> (raw)
In-Reply-To: <20090223030014.GE26056@adacore.com>

> Date: Sun, 22 Feb 2009 19:00:14 -0800
> From: Joel Brobecker <brobecker@adacore.com>
> 
> > > 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.


  reply	other threads:[~2009-02-23  4:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12 16:24 Aleksandar Ristovski
2009-02-23  2:52 ` Joel Brobecker
2009-02-23  3:00   ` Daniel Jacobowitz
2009-02-23  3:13     ` Joel Brobecker
2009-02-23  8:53       ` Eli Zaretskii [this message]
2009-02-23 16:18         ` Aleksandar Ristovski
2009-02-24  1:32           ` Eli Zaretskii
2009-02-23  8:56     ` Mark Kettenis
2009-02-23 16:26       ` Aleksandar Ristovski
2009-02-23 17:15         ` Daniel Jacobowitz
2009-02-23 17:36           ` Joel Brobecker
2009-02-23 18:24             ` Aleksandar Ristovski
2009-02-23 20:02               ` Aleksandar Ristovski
2009-02-27 20:36                 ` Joel Brobecker
2009-03-04 21:47                   ` Aleksandar Ristovski
2009-03-05 19:12                     ` Joel Brobecker
2009-03-05 19:22                       ` Daniel Jacobowitz
2009-03-05 19:27                         ` Aleksandar Ristovski
2009-03-05 19:35                           ` Daniel Jacobowitz
2009-03-05 22:50                             ` Joel Brobecker
2009-03-05 23:08                               ` Daniel Jacobowitz
2009-03-06  5:00                                 ` Aleksandar Ristovski
2009-03-06 12:25                                   ` Daniel Jacobowitz
2009-03-06 14:52                                     ` Aleksandar Ristovski
2009-04-01 18:50                                       ` Joel Brobecker
2009-04-01 19:16                                         ` Aleksandar Ristovski
2009-02-24 20:24               ` Maciej W. Rozycki
2009-02-25  2:15                 ` Aleksandar Ristovski
2009-02-25  7:04                   ` Maciej W. Rozycki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=u8wnxu77c.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=aristovski@qnx.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox