From: "Eli Zaretskii" <eliz@gnu.org>
To: Orjan Friberg <orjan.friberg@axis.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [commit/cris] Add guru mode setting for CRISv32
Date: Sat, 14 May 2005 07:13:00 -0000 [thread overview]
Message-ID: <01c557e2$Blat.v2.4$b5db4a00@zahav.net.il> (raw)
In-Reply-To: <4284C537.9060106@axis.com> (message from Orjan Friberg on Fri, 13 May 2005 17:18:15 +0200)
> Date: Fri, 13 May 2005 17:18:15 +0200
> From: Orjan Friberg <orjan.friberg@axis.com>
> CC: gdb-patches@sources.redhat.com
>
> I'm sorry; I hadn't even realized there was a CRIS section in the manual.
>
> Ok to commit?
>
> 2005-05-13 Orjan Friberg <orjanf@axis.com>
>
> * gdb.texinfo (CRIS): Update the cris-version and cris-dwarf2-cfi
> documentation. Add documentation for cris-mode.
Yes, but...
> @item show cris-dwarf2-cfi
> Show the current state of using DWARF-2 CFI.
> @end table
>
> +@item set cris-mode @var{mode}
@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.)
> +@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{CRIS_MODE_GURU} (the default is @samp{CRIS_MODE_NORMAL}).
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?
> +@item show cris-mode
> +Show the current CRIS mode.
The @end table should go after this part.
Thanks for a timely response.
next prev parent reply other threads:[~2005-05-13 17:42 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 [this message]
2005-05-23 11:27 ` Orjan Friberg
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='01c557e2$Blat.v2.4$b5db4a00@zahav.net.il' \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=orjan.friberg@axis.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