Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Tedeschi\, Walfred" <walfred.tedeschi@intel.com>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [PATCH V2] ABI changes for MPX.
Date: Fri, 18 Dec 2015 15:11:00 -0000	[thread overview]
Message-ID: <83poy3x03a.fsf@gnu.org> (raw)
In-Reply-To: <AC542571535E904D8E8ADAE745D60B1944507386@IRSMSX104.ger.corp.intel.com>	(walfred.tedeschi@intel.com)

> From: "Tedeschi, Walfred" <walfred.tedeschi@intel.com>
> CC: "brobecker@adacore.com" <brobecker@adacore.com>,	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> Date: Thu, 17 Dec 2015 16:44:47 +0000
> 
> You issue the command "return a", where a is a pointer.
> BND0 should contain that boundary of a, but it will in fact return any value presented in the register at that moment.
> In this way application will be in a not good state.  Continuing the execution the user might have a bound violation due to the return.
> This behaviour is when the " mpx-bnd-init-on-return" is 0.
> 
> In case the " mpx-bnd-init-on-return" is 1 the BND0 will be set to zero, INIT state, and the pointer a will be able to access the whole memory.

Thanks, I understand now.  So why would a GDB user want to set
mpx-bnd-init-on-return to zero?  The result will always be a bound
violation, no?


  reply	other threads:[~2015-12-18 15:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 13:24 Walfred Tedeschi
2015-12-17 16:35 ` Eli Zaretskii
2015-12-17 16:44   ` Tedeschi, Walfred
2015-12-18 15:11     ` Eli Zaretskii [this message]
2015-12-18 17:24       ` Joel Brobecker
2015-12-19  8:16         ` Eli Zaretskii
2015-12-18 17:19 ` Joel Brobecker

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=83poy3x03a.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=walfred.tedeschi@intel.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