From: Pedro Alves <palves@redhat.com>
To: Walfred Tedeschi <walfred.tedeschi@intel.com>,
eliz@gnu.org, brobecker@adacore.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH V5 5/5] ntel MPX bound violation handling
Date: Tue, 02 Feb 2016 10:38:00 -0000 [thread overview]
Message-ID: <56B0871F.6060201@redhat.com> (raw)
In-Reply-To: <56B08055.1060507@intel.com>
On 02/02/2016 10:09 AM, Walfred Tedeschi wrote:
> Am 1/28/2016 um 2:42 PM schrieb Pedro Alves:
> Pedro,
>
> I have tried to address all your comments.
I quickly skimmed v6 (will have to look in more detail), but looks like
you missed the renaming comments. See them quoted below.
> For the tests I also verified that there was only one line in the log as
> shown in the wiki.
Thanks.
> Have though some comments below:
>
>> # Function called when a segmentation fault with
>> # SIGCODE 3 (SIG_CODE_BOUNDARY_FAULT) is received by the inferior.
>>
>> But, see below.
>>> +
>>> +static void
>>> +handle_segmentation_faults (struct ui_out *uiout)
>>
>> "handle_segmentation_fault", singular.
...
>> And then the gdbarch hook can be renamed to a more generic
>> gdbarch_handle_segmentation_fault.
...
The comments thoughout should be
>> updated then, like, for this function:
>>
>> /* Some targets/architectures can do extra processing/display of
>> segmentation faults. E.g., Intel MPX boundary faults.
>> Call the architecture dependent function to handle the fault. */
>>
>> static void
>> handle_segmentation_fault (struct ui_out *uiout)
>> {
>>
(You did update the comment.)
>>> +for {set i 0} {$i < 15} {incr i} {
>>> + set message "MPX signal segv Upper: ${i}"
>>> + gdb_test_multiple "continue" "$message ${i}" {
>>> + -re $segv_upper_bound {
>>> + pass "$message"
>>> + }
>>> + -re ".*$inferior_exited_re normally.*$gdb_prompt $" {
>>> + fail "$message"
>>
>> The pass/fail calls are missing ${i}. Please make sure test
>> messages are unique in gdb.sum:
>
> In fail and pass i think we do not need the ${i} it is added at the
> message level already see:
>
> set message "MPX signal segv Upper: ${i}"
In that case, you shouldn't have an "${i}" in this line:
+ gdb_test_multiple "continue" "$message ${i}" {
because then that expands to "... ${i} ${i}".
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-02-02 10:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 15:36 [PATCH V5 0/5] Intel MPX bound violation support Walfred Tedeschi
2016-01-22 15:17 ` [PATCH V5 1/5] Preparation for new siginfo on Linux Walfred Tedeschi
2016-01-28 12:20 ` Pedro Alves
2016-01-22 15:17 ` [PATCH V5 4/5] Adaptation of siginfo fixup for the new bnd fields Walfred Tedeschi
2016-01-28 12:37 ` Pedro Alves
2016-02-02 10:31 ` Pedro Alves
2016-02-02 13:58 ` Walfred Tedeschi
2016-01-22 15:17 ` [PATCH V5 3/5] Add bound related fields to the siginfo structure Walfred Tedeschi
2016-01-28 12:23 ` Pedro Alves
2016-01-22 15:18 ` [PATCH V5 5/5] ntel MPX bound violation handling Walfred Tedeschi
2016-01-28 13:43 ` Pedro Alves
2016-01-28 13:49 ` Walfred Tedeschi
2016-01-28 14:18 ` Pedro Alves
2016-02-02 10:09 ` Walfred Tedeschi
2016-02-02 10:38 ` Pedro Alves [this message]
2016-02-02 10:41 ` Walfred Tedeschi
2016-01-22 15:18 ` [PATCH V5 2/5] Use linux_get_siginfo_type_with_fields for x86 Walfred Tedeschi
2016-01-28 12:19 ` Pedro Alves
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=56B0871F.6060201@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--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