From: Yao Qi <qiyaoltc@gmail.com>
To: Walfred Tedeschi <walfred.tedeschi@intel.com>
Cc: palves@redhat.com, brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: [PATCH V5 1/2] Initialize bnd register before performing inferior calls.
Date: Tue, 26 Apr 2016 14:08:00 -0000 [thread overview]
Message-ID: <86vb34fopi.fsf@gmail.com> (raw)
In-Reply-To: <1458310565-19980-1-git-send-email-walfred.tedeschi@intel.com> (Walfred Tedeschi's message of "Fri, 18 Mar 2016 15:16:05 +0100")
Walfred Tedeschi <walfred.tedeschi@intel.com> writes:
> BND registers should be initialized before performing an inferior call
> to avoid undesired bound violations.
What are the undesired bound violations? Do have an example?
Resetting BND registers in the inferior call isn't right to me, the BND
setting isn't in effect in the inferior call. If the function can
trigger bound violations, it is expected that it still can trigger
violations in the inferior call.
--
yao (齐尧)
prev parent reply other threads:[~2016-04-26 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 14:16 Walfred Tedeschi
2016-04-26 14:08 ` Yao Qi [this message]
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=86vb34fopi.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).