Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Aleksandar Ristovski <aristovski@qnx.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] mips-tdep: info registers
Date: Tue, 24 Feb 2009 01:32:00 -0000	[thread overview]
Message-ID: <uiqn0rkfy.fsf@gnu.org> (raw)
In-Reply-To: <gnuhff$kmv$1@ger.gmane.org>

> From:  Aleksandar Ristovski <aristovski@qnx.com>
> Date:  Mon, 23 Feb 2009 11:05:03 -0500
> 
> > I agree.  Documenting it would be good, thanks.
> > 
> 
> I added a note about the regno syntax.

Thank you.

> ChangeLog:
> 
> * gdb.texinfo (info registers): Add a note about permitted
> info registers regno syntax.

The string in parentheses should be the name of the node in which you
made a change, in this case "Registers".

> 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.

This is fine, thanks.


  reply	other threads:[~2009-02-23 20:02 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
2009-02-23 16:18         ` Aleksandar Ristovski
2009-02-24  1:32           ` Eli Zaretskii [this message]
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=uiqn0rkfy.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=aristovski@qnx.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