This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH v1] ABI changes for Intel(R) MPX.
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Walfred Tedeschi <walfred dot tedeschi at intel dot com>
- Cc: palves at redhat dot com, brobecker at adacore dot com, gdb-patches at sourceware dot org
- Date: Mon, 26 Oct 2015 18:11:56 +0200
- Subject: Re: [PATCH v1] ABI changes for Intel(R) MPX.
- Authentication-results: sourceware.org; auth=none
- References: <1445864086-4831-1-git-send-email-walfred dot tedeschi at intel dot com> <1445864086-4831-6-git-send-email-walfred dot tedeschi at intel dot com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Walfred Tedeschi <walfred.tedeschi@intel.com>
> Cc: gdb-patches@sourceware.org, Walfred Tedeschi <walfred.tedeschi@intel.com>
> Date: Mon, 26 Oct 2015 13:54:46 +0100
>
> doc:
> gdb.texinfo: (Intel(R) Memory Protection Extensions): Add
> documentation on performing program function calls.
Is it possible to lose the "(R)" part here? It gets in the way of
Emacs syntax highlighting of ChangeLog entries.
> +While calling functions of an MPX enabled program boundary registers have
> +to be initialized before performing the call. Intended to avoid unexpected
> +side effects, as receiving a bound violation signal while performing
> +the operation. Nevertheless is possible to change the boundary values if
> +desired in placing a breakpoint at the end of the prologue and setting
> +bound registers as wished.
> +After the call is performed bound register might be keept or not for
> +further investigations. The behaviour of initializing bounds on returning
> +from a program function calls can be controlled and vizualized via the commands
> +@table @code
> +@kindex set mpx-bnd-init-on-return
> +When set to 1 bound registers will be initialized when returning from a
> +calling a program function
> +@kindex show mpx-bnd-init-on-return
> +Show the state of mpx-bnd-init-on-return.
> +@end table
There are a few English and Texinfo issues here, so I suggest the
following minor rewording (please make sure I didn't change the
meaning of what you intended to say):
While calling functions of an MPX enabled program, boundary registers have
to be initialized before performing the call, to avoid unexpected side
effects, such as a bound violation exception, while performing the
operation. Nevertheless, is possible to change the boundary values, if
desired, by placing a breakpoint at the end of the prologue and setting
bound registers as wished in the commands of that breakpoint.
After the call is performed, a bound register might or might not be keept for
further investigations. The behaviour of initializing bounds on returning
from a program function calls can be controlled and displayed using the
following commands:
@table @code
@kindex set mpx-bnd-init-on-return
@item set mpx-bnd-init-on-return
When set to 1, bound registers will be initialized when returning from a
calling a program function.
@kindex show mpx-bnd-init-on-return
@item show mpx-bnd-init-on-return
Show the state of @code{mpx-bnd-init-on-return}.
@end table
Thanks.