From: Orjan Friberg <orjan.friberg@axis.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit/cris] Add guru mode setting for CRISv32
Date: Mon, 23 May 2005 11:27:00 -0000 [thread overview]
Message-ID: <4291B4FF.9090907@axis.com> (raw)
In-Reply-To: <01c557e2$Blat.v2.4$b5db4a00@zahav.net.il>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
Eli Zaretskii wrote:
>
> @item is only valid inside a @table, so @end table needs to be moved
> after the 2 new @items you added. (It is worthwhile to try to produce
> the manual after you make a change in the *.texinfo files, since then
> makeinfo will point out any problems.)
Got it.
> What are CRIS_MODE_GURU and CRIS_MODE_NORMAL? are they literal strings
> or some symbols? That is, do I type
>
> (gdb) set cris-mode CRIS_MODE_GURU
>
> ? If so, why are they in CAPS?
Now that you mention it, it does look strange. I changed it to 'guru' and
'normal' (both in the code and the documentation).
>>+@item show cris-mode
>>+Show the current CRIS mode.
>
>
> The @end table should go after this part.
Fixed.
> Thanks for a timely response.
Thank you. Committed the following:
2005-05-23 Orjan Friberg <orjanf@axis.com>
* gdb.texinfo (CRIS): Update the cris-version and cris-dwarf2-cfi
documentation. Add documentation for cris-mode.
--
Orjan Friberg
Axis Communications
[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 1563 bytes --]
Index: gdb.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.255
diff -u -r1.255 gdb.texinfo
--- gdb.texinfo 20 May 2005 14:58:38 -0000 1.255
+++ gdb.texinfo 23 May 2005 10:39:02 -0000
@@ -14665,21 +14665,30 @@
@table @code
@item set cris-version @var{ver}
@cindex CRIS version
-Set the current CRIS version to @var{ver}. The CRIS version affects
-register names and sizes. This command is useful in case
-autodetection of the CRIS version fails.
+Set the current CRIS version to @var{ver}, either @samp{10} or @samp{32}.
+The CRIS version affects register names and sizes. This command is useful in
+case autodetection of the CRIS version fails.
@item show cris-version
Show the current CRIS version.
@item set cris-dwarf2-cfi
@cindex DWARF-2 CFI and CRIS
-Set the usage of DWARF-2 CFI for CRIS debugging. The default is off
-if using @code{gcc-cris} whose version is below @code{R59}, otherwise
-on.
+Set the usage of DWARF-2 CFI for CRIS debugging. The default is @samp{on}.
+Change to @samp{off} when using @code{gcc-cris} whose version is below
+@code{R59}.
@item show cris-dwarf2-cfi
Show the current state of using DWARF-2 CFI.
+
+@item set cris-mode @var{mode}
+@cindex CRIS mode
+Set the current CRIS mode to @var{mode}. It should only be changed when
+debugging in guru mode, in which case it should be set to
+@samp{guru} (the default is @samp{normal}).
+
+@item show cris-mode
+Show the current CRIS mode.
@end table
@node Super-H
next prev parent reply other threads:[~2005-05-23 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 13:18 Orjan Friberg
2005-05-13 15:18 ` Eli Zaretskii
2005-05-13 17:37 ` Orjan Friberg
2005-05-14 6:10 ` Eli Zaretskii
2005-05-13 17:42 ` Orjan Friberg
2005-05-14 7:13 ` Eli Zaretskii
2005-05-23 11:27 ` Orjan Friberg [this message]
2005-05-24 1:36 ` 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=4291B4FF.9090907@axis.com \
--to=orjan.friberg@axis.com \
--cc=eliz@gnu.org \
--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