From: Pedro Alves <palves@redhat.com>
To: "Tedeschi, Walfred" <walfred.tedeschi@intel.com>,
qiyaoltc@gmail.com, brobecker@adacore.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH V7] amd64-mpx: initialize bnd register before performing inferior calls.
Date: Tue, 14 Feb 2017 13:59:00 -0000 [thread overview]
Message-ID: <e56a89ba-9187-31e7-d339-d51af91c3e61@redhat.com> (raw)
In-Reply-To: <a21e3508-ac20-9a17-8bba-3644cdc3bb52@intel.com>
On 02/14/2017 01:34 PM, Tedeschi, Walfred wrote:
> On 02/13/2017 09:33 AM, Tedeschi, Walfred wrote:
>> At the inferior call time all BND registers are set to the INIT state.
>> That covers 90% of the usage case and keeps the actual behavior of GDB.
>> In case it is desirable to investigate any bound violation user can
>> add a breakpoint on the prolog of the function and
>> set the BND register there, I understand that this is the normal use
>> case for the debugger as well.
> In reality it did not work as expected. When an inferior call is done
> and there is a breakpoint in the executed GDB issues a message like:
>
> "The program being debugged stopped while in a function called from GDB.
> Evaluation of the expression containing the function
> (foo) will be abandoned.
> When the function is done executing, GDB will silently stop."
This looks normal. What were you expecting instead?
> Also after that no signal generated within the function call is reported.
Please clarify.
> Not sure if this a limitation or a bug. In case you think it is a bug i
> can add some entries in Bugzilla.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-02-14 13:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 15:13 Walfred Tedeschi
2017-02-06 17:05 ` [ping] " Tedeschi, Walfred
2017-02-06 17:58 ` Pedro Alves
2017-02-07 8:56 ` Tedeschi, Walfred
2017-02-08 12:27 ` Pedro Alves
2017-02-08 16:21 ` Pedro Alves
2017-02-08 16:31 ` Tedeschi, Walfred
2017-02-13 8:33 ` Tedeschi, Walfred
[not found] ` <75843d02-1b8b-f726-c36d-cd05c0ea5339@redhat.com>
2017-02-13 12:55 ` Tedeschi, Walfred
2017-02-14 13:35 ` Tedeschi, Walfred
2017-02-14 13:59 ` Pedro Alves [this message]
2017-02-15 13:02 ` Tedeschi, Walfred
2017-02-15 13:15 ` Pedro Alves
2017-02-16 13:50 ` Tedeschi, Walfred
2017-02-16 14:52 ` Pedro Alves
2017-02-16 15:37 ` Tedeschi, Walfred
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=e56a89ba-9187-31e7-d339-d51af91c3e61@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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