This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: RFC: Use the ARM CPSR as a fallback to determine ARM/Thumb
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Daniel Jacobowitz <drow at false dot org>
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 02 May 2008 13:17:06 +0300
- Subject: Re: RFC: Use the ARM CPSR as a fallback to determine ARM/Thumb
- References: <20060220214918.GA28798@nevyn.them.org> <1140519913.27380.29.camel@pc960.cambridge.arm.com> <20060221153601.GA21183@nevyn.them.org> <20060302221446.GA18830@nevyn.them.org> <20080501183805.GA22218@caradoc.them.org>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Thu, 1 May 2008 14:38:05 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Eli Zaretskii <eliz@gnu.org>
>
> Eli, do the documentation and NEWS changes look OK?
Yes, but I have a few comments:
> +@item set arm fallback-mode
> +This command sets the mode (ARM versus Thumb) which @value{GDBN} will
> +assume for code without a symbol table. The default is @samp{auto},
> +which causes @value{GDBN} to use the mode associated with the current
> +CPSR.
Please explain (in parens or in a @footnote) what is CPSR. There's no
other instance in the manual where this acronym is used.
Also, I think we should list all possible values of this option
explicitly. As written, the text forces the user to gather the values
incrementally (first ARM and Thumb, then auto), and leaves me
wondering whether there are more possible values.
> +set arm fallback-mode (arm|thumb|auto)
> +show arm fallback-mode
> +set arm force-mode (arm|thumb|auto)
> +show arm force-mode
> + These variables control how ARM GDB determines whether instructions
^^^^^^^^^
"commands", not "variables", I think.
> + are ARM or Thumb. The default for both settings is auto, which uses
> + the current CPSR value for instructions without symbols; previous
> + versions of GDB behaved as if "set arm fallback-mode arm".
Btw, I find this description much better than the one in gdb.texinfo:
here you explicitly talk about instructions, whereas in the manual the
description is much more abstract and doesn't even mention
instructions. Can we make the manual closer to NEWS in this sense?
Thanks.