Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stephane Carrez <stcarrez@nerim.fr>
To: gdb-patches@sources.redhat.com
Subject: [RFA]: Document tui reg commands
Date: Fri, 19 Mar 2004 00:09:00 -0000	[thread overview]
Message-ID: <405318FE.8000904@nerim.fr> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 201 bytes --]

Hi!

This is the documentation part of the new TUI reg commands.

Ok to commit?

	Stephane

2004-03-13  Stephane Carrez  <stcarrez@nerim.fr>

	* gdb.texinfo (TUI Commands): Document tui reg commands.


[-- Attachment #1.2: doc.diffs --]
[-- Type: text/plain, Size: 1086 bytes --]

Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.200
diff -u -p -r1.200 gdb.texinfo
--- doc/gdb.texinfo	9 Mar 2004 16:16:35 -0000	1.200
+++ doc/gdb.texinfo	13 Mar 2004 13:24:43 -0000
@@ -14232,6 +14232,25 @@ can be affected to another window.
 @item refresh
 @kindex refresh
 Refresh the screen.  This is similar to using @key{C-L} key.
+
+@item tui reg float
+@kindex tui reg float
+Show the floating point registers in the register window.
+
+@item tui reg general
+@kindex tui reg general
+Show the general registers in the register window.
+
+@item tui reg next
+@kindex tui reg next
+Show the next register group.  The list of register groups as well as
+their order is target specific.  The predefined register groups are the
+following: @code{general}, @code{float}, @code{system}, @code{vector},
+@code{all}, @code{save}, @code{restore}.
+
+@item tui reg system
+@kindex tui reg system
+Show the system registers in the register window.
 
 @item update
 @kindex update

[-- Attachment #2: Type: application/pgp-signature, Size: 253 bytes --]

WARNING: multiple messages have this Message-ID
From: Stephane Carrez <stcarrez@nerim.fr>
To: gdb-patches@sources.redhat.com
Subject: [RFA]: Document tui reg commands
Date: Sat, 13 Mar 2004 14:21:00 -0000	[thread overview]
Message-ID: <405318FE.8000904@nerim.fr> (raw)
Message-ID: <20040313142100.mgZ27nRU7canwn-wXgfzNA55UkpeuRLTxVYzmBj9-ro@z> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 201 bytes --]

Hi!

This is the documentation part of the new TUI reg commands.

Ok to commit?

	Stephane

2004-03-13  Stephane Carrez  <stcarrez@nerim.fr>

	* gdb.texinfo (TUI Commands): Document tui reg commands.


[-- Attachment #1.2: doc.diffs --]
[-- Type: text/plain, Size: 1086 bytes --]

Index: doc/gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.200
diff -u -p -r1.200 gdb.texinfo
--- doc/gdb.texinfo	9 Mar 2004 16:16:35 -0000	1.200
+++ doc/gdb.texinfo	13 Mar 2004 13:24:43 -0000
@@ -14232,6 +14232,25 @@ can be affected to another window.
 @item refresh
 @kindex refresh
 Refresh the screen.  This is similar to using @key{C-L} key.
+
+@item tui reg float
+@kindex tui reg float
+Show the floating point registers in the register window.
+
+@item tui reg general
+@kindex tui reg general
+Show the general registers in the register window.
+
+@item tui reg next
+@kindex tui reg next
+Show the next register group.  The list of register groups as well as
+their order is target specific.  The predefined register groups are the
+following: @code{general}, @code{float}, @code{system}, @code{vector},
+@code{all}, @code{save}, @code{restore}.
+
+@item tui reg system
+@kindex tui reg system
+Show the system registers in the register window.
 
 @item update
 @kindex update

[-- Attachment #2: Type: application/pgp-signature, Size: 253 bytes --]

             reply	other threads:[~2004-03-13 14:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19  0:09 Stephane Carrez [this message]
2004-03-13 14:21 ` Stephane Carrez
2004-03-19  0:09 ` Eli Zaretskii
2004-03-13 16:23   ` Eli Zaretskii
2004-03-28 12:32   ` Stephane Carrez
2004-03-28 13:40     ` Eli Zaretskii

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=405318FE.8000904@nerim.fr \
    --to=stcarrez@nerim.fr \
    --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