From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Omair Javaid <omair.javaid@linaro.org>
Cc: Pedro Alves <palves@redhat.com>, Yao Qi <qiyaoltc@gmail.com>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [commit] aarch64: PR 19806: watchpoints: false negatives + PR 20207 contiguous ones
Date: Mon, 07 May 2018 08:36:00 -0000 [thread overview]
Message-ID: <20180507083635.GA41899@host1.jankratochvil.net> (raw)
In-Reply-To: <CANW4E-2VdPMuo2QR1R3E_M+w34_1pms7APHCiGYWWCeUmsH2Hg@mail.gmail.com>
On Mon, 07 May 2018 10:02:57 +0200, Omair Javaid wrote:
> On 5 May 2018 at 01:47, Pedro Alves <palves@redhat.com> wrote:
> > On 05/04/2018 09:30 PM, Jan Kratochvil wrote:
> >> Checked in:
> >> a3b60e4588606354b93508a0008a5ca04b68fad8
>
> New watchpoint-unaligned.exp test introduced by this commit fails for
> arm targets. (Tested with Raspberry Pi2 Tester)
I have described that in the commit log:
There remains one issue:
kernel-4.15.14-300.fc27.armv7hl
FAIL: gdb.base/watchpoint-unaligned.exp: continue
FAIL: gdb.base/watchpoint-unaligned.exp: continue
(gdb) continue
Continuing.
Unexpected error setting watchpoint: Invalid argument.
(gdb) FAIL: gdb.base/watchpoint-unaligned.exp: continue
But that looks as a kernel bug to me.
(1) It is not a regression by this patch.
(2) It is unrelated to this patch.
I do not have ARM32 machine for testing, I did find out the FAIL on
https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers
arm03-packager00.cloud.fedoraproject.org
arm03-packager01.cloud.fedoraproject.org
but that does not have too recent kernel and I haven't found an ARM32 machine
with newer kernel, both such allocations failed for me inside Red Hat:
Fedora-28-20180427.n.0 armhfp https://beaker.engineering.redhat.com/recipes/5107255
Fedora-Rawhide-20180502.n.0 armhfp https://beaker.engineering.redhat.com/recipes/5106357
due to:
Question
The following error occurred while installing the boot loader. The system will
not be bootable. Would you like to ignore this and continue with installation?
boot loader install failed
Please respond 'yes' or 'no':
It is true I could file some tracker PR for such XFAIL but then it looks to me
as it would get more easily forgotten while this existing ARM32 bug unrelated
to this my aarch64 fix should be probably fixed soon.
One should also bisect GDB if it isn't a regression. But TBH professionally
AFAIK I am also not so much interested in ARM32.
> I have not tested it for other targets but if this is AArch64 specific
> kindly mark it an XFail for other targets.
I have marked it as XFAIL for all targets where it makes sense and which
I could test.
Jan
next prev parent reply other threads:[~2018-05-07 8:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 21:08 [patch] " Jan Kratochvil
2017-06-19 13:43 ` ping: " Jan Kratochvil
2017-06-19 13:44 ` Jan Kratochvil
2017-10-18 19:52 ` ping#2: " Jan Kratochvil
2017-10-30 11:27 ` Yao Qi
2017-11-03 22:04 ` Jan Kratochvil
2018-03-21 19:03 ` ping: " Jan Kratochvil
2018-04-20 14:49 ` Pedro Alves
2018-04-20 14:56 ` Pedro Alves
2018-04-20 15:54 ` Eli Zaretskii
2018-04-20 15:59 ` Pedro Alves
2018-04-26 20:12 ` Jan Kratochvil
2018-05-01 23:03 ` Jan Kratochvil
2018-05-01 23:06 ` Jan Kratochvil
2018-05-02 14:50 ` Eli Zaretskii
2018-05-03 9:16 ` Jan Kratochvil
2018-05-03 9:18 ` Jan Kratochvil
2018-05-04 16:40 ` Pedro Alves
2018-05-04 20:30 ` [commit] " Jan Kratochvil
2018-05-04 20:47 ` Pedro Alves
2018-05-07 8:03 ` Omair Javaid
2018-05-07 8:36 ` Jan Kratochvil [this message]
2018-05-08 12:08 ` [patch] " Ulrich Weigand
2018-05-08 12:27 ` [obv] watchpoint-unaligned.exp: Use skip_hw_watchpoint_tests [Re: [patch] aarch64: PR 19806: watchpoints: false negatives + PR 20207 contiguous ones] Jan Kratochvil
2018-05-08 12:45 ` [obv] watchpoint-unaligned.exp: Use skip_hw_watchpoint_tests [Re: [patch] aarch64: PR 19806: watchpoints: false negatives + PR Ulrich Weigand
2017-10-30 11:31 ` ping#2: [patch] aarch64: PR 19806: watchpoints: false negatives + PR 20207 contiguous ones Yao Qi
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=20180507083635.GA41899@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=omair.javaid@linaro.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.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).